Related
I'm thinking of another ROM line, to be good enough to use for business (so it has to be very stable) and with toned down, professional graphics. This will very much be a "clean" ROM, with no extra BS apps or addons. Can I hear some suggestions please ?
Looking forward to it..
As you already know, I'm not a huge fan of the HTC apps/enhancements, so I would leave those out with the option of installing via cab, or have them in the ROM with a working toggle to turn them off.
I would say do as many of the "under the hood" tweaks you can do without sacrificing stability.
As for graphics, I already like your taskbar in your WM6.5 series, and I think that could stay. I'm not sure what changes you would have in mind for graphics, but I think the graphics you have now are pretty clean.
Are you thinking of a WM6.5 ROM or a WM6.1 ROM? I didn't see that mentioned, so I thought I would ask since you've done both in the past.
i think you should go with stock graphics people customize if they choose. my ideal business rom would be like juicy's cdma one
"It's business, It's business time!" - Flight of the Conchords
I think this is a GREAT idea. Would this be 6.1 or 6.5? 6.5 is very close to being capable of generating a "stable" ROM.
Even though this is business oriented, I think anyone would much appreciate the style (icons, themes, graphics) that you put into your ROMs. Same would hold true for most of the enhancements. Maybe trim down some of the fluff.
simple is the Best
go for it am sure will be a good Rom.
Good Luck
WOW, another one. jeez, you gonna be busy LOL. I get frustrated sometimes with just the one version. More power to ya
What about a stock looking version? I know some people would like a ROM that is much better than the crappy one that comes preinstalled. I think you might get a lot of hits from a lighter ROM that looks semi-stock. As stable as stock, but with all the enhancements and tweaks you can squeeze into it. Possibly a 6.5 and 6.1 version.
I think it's a very good idea and in my opinion the ROM must be based on WM 6.1. Email/SMS/MMS/Vido call/WIfi/ must work without a hitch. You could include opera 9.7b and maybe IE 8.
These are my suggestions. Merci.
P.S. i only use your roms!
mdalacu said:
I think it's a very good idea and in my opinion the ROM must be based on WM 6.1. Email/SMS/MMS/Vido call/WIfi/ must work without a hitch. You could include opera 9.7b and maybe IE 8.
These are my suggestions. Merci.
P.S. i only use your roms!
Click to expand...
Click to collapse
Newer versions of PIE only work with 6.5 as far as I know. I agree that the most stable ROM is going to be 6.1, but if you go with 6.5 I would suggest an older build. 23001 seems like a turd to me. Went back to 21820 and its twice as fast with no bugs.
3 important things for a business ROM:
1. As clean as possible (only essential progs. installed, like Pim Backup, Adobe Reader, Pocket RAR, Google Maps, GPS Test)
2. Stable = reliable
3. Good battery life
jmckeejr said:
23001 seems like a turd to me. Went back to 21820 and its twice as fast with no bugs.
Click to expand...
Click to collapse
lol i know what you mean
I have reverted back to 21018. After playing around with 4 later builds and a little go with 6.5 I am back here to old faithful. Very fast, battery burns lean, and every build i have tried later than this had some problem or other. slow/buggy or battery destroyer.
Easy to Use Dialer
Dialer:...................Accurate - consistent - easy to use - good speaker phone / mute / automated menu support
Three interfaces:....TF3D2 – Titanium – Win Phone Basic Text interface
Graphics:...............Clean with color - Landscape mode 6.1 style (quick easy buttons) Portrait Mode Action softkey
GPS:.....................Good stand alone support (no data plan)
MMS:....................Support for the largest attachments the carriers will allow
SMS:....................Good support for text conversations
Weather:...............Good support for text and graphic reports in all interfaces
Stocks:.................Good support for text and graphic reports in all interfaces
Wifi / Networking:...Corporate and HotSpot support
Programs Tab:........(TD3D2) 3 or 4 column option with app names under icons
Good battery life Business does not mean Boring – It means Practical Predictable Performance
Apps
I would say:
Remote Desktop
World Card
Adobe Reader
Office Suite (obviously)
Google Maps AND Live Search
All of the basics for GPS- QuickGPS, aGPS settings, etc.
Live Messenger (for Office Communicator support)
Those are the 'business' tools that I use most. Does that help?
yes yes yes
thank you for start takeing this as trend
please under the hood basic application
some applications in my rom i cant even remember when i used them
the most imprtant is Battary vs application ( i have charger at the car,home , office., .......poof....)
any small clock tic will eat somthing from the phone
Ram and heat.
my x1 cracked because of the heat, my ear after a good call get fride.
some rams goes above 60%
example i tried yesterday to put my phone in full withe new cocked rom( backlight full and battery power on ) the battarey draind in less than 2 hours, without any call or sms ... nothing
but applications like email,office,sms,organizer and contacts will be fine
yes please Business Edition is great what ever under the hood
Loved the Energy Rom3......but it was lacking (I could not find anyways) Voice Command applet. I use blue-tooth headset continually and have calls/messaging/reminders etc routed thru blue-tooth headset. Would love to see that in the business edition. That's mostly what this phone is used for.
bassam said:
example i tried yesterday to put my phone in full withe new cocked rom... ...nothing
Click to expand...
Click to collapse
Those **** roms are terrible...
This is an awesome idea... The chrome version was cool... but perhaps more emphasis on productivity. A nice action screen that brings up all of the things you would use on a daily basis and keeps them right at your fingertips... I know I need to take notes at a moments notice in my job... and it's hard to get things where I need them to be sometimes...
Also contacts and appointments are of the utmost importance... Constantly scheduling things and changing them around, it's nice to have things in an easily accessible spot...
Though I don't spend much time on the phone lately... I would imagine bluetooth would be crucial as well... and having as much control from the headset as possible would also be nice...
Then of course some "hey check me out *****es" graphics and apps that are streamlined and professional looking enough to show your boss when you pull the phone out and he asks "what the hell is that thing?"
That's just my $ 750,500,000 ZWD
Quite honestly, your current ROM is fit for business and displays appropriate graphics and tones. The add-ons are typically ones the manufacturers have missed and allow a much better experience than stock. I work with professionals everyday and when I show off ROM's from XDA, they often say if I had seen that at ATT or T-Mobile, I would have purchased this phone vs. Blackberry or iPhone.
This sounds like what I've been waiting for!
A simple WM6.5 interface that is stable and fast. No touchflo, as we all know that is not for business users. I think the best thing for this special business line, is that all the under the hood settings come pre-configured, and don't give us the option to make advanced config changes. I seriously waste so much time trying to tinker with the settings, and eventually make the device less stable.
Also this line should have one application for each function. I rarely need 15 chat clients, and 10 media apps!
Great idea.. Make sure to add Stock and Weather to Chome 6.5 These are helpful for those business travelers on the go with an eye on the market.. The JML Stocks plugin is sweet!!!!
Is this really needed?
I'm nearly new with this machine, but a very heavy Bussiness user of HTC PDAs for 5 years.
Comming from an Hermes, I have flashed your Energy Magic Rom 20090630 after two week of trying the stock one and threads reading here, and for me your main rom is fast, accurate, conservative with battery and completly perfect for work.
If someone feel titanium or tf3d improductive, it could be dissable. And the same could be done with the new menus and notification style.... To change three or four options in the default behaviour of your rom, that could be made with a few clicks here and there, don't justify a new line of roms.
Just my though...
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 .
just curious if anyone switched back to WM6.5 after trying android on HD2 ? any particular reasons ?
After being an exclusive Windows Mobile user from the Pocket PC days in 2001, I tried Android on my HTC HD2 with great fear and trepidation. After 2 months i am VERY satisfied with Android and can't imagine ever going back.
Good luck with your decision.
never left WM, just run android on SD card
here more statements
I only tried one rom, it didn't work that well, and I hated not being able to customise it how I liked.
I absolutley hate sense/titanium/spb mobile shell... none of them work as well as my setup, I have my phone doing exactly what I want, when I want, and everything I use or need to see at all times is on my today screen. No other UI can currently give me that.
Every OS upgrade has brought less usability at the expense of 'looking nice', I hate having to go through multiple screens to do something as simple as turn on bluetooth and start a media player, one click for me and it's done. Same for many things.
I tried American Android on my HTC HD2. Battery life on all android sucks, so I am back on WM6.5. I am very sad Microsoft switched to WP7 after 6.5 is so cool.
Android must take care of battery management before releasing OS as now it just ruins the pleasure of Android OS. My WinMo6.5 lasts more than 4 days on one charge. I wanna see Android doing this
bbobeckyj said:
I only tried one rom, it didn't work that well, and I hated not being able to customise it how I liked.
I absolutley hate sense/titanium/spb mobile shell... none of them work as well as my setup, I have my phone doing exactly what I want, when I want, and everything I use or need to see at all times is on my today screen. No other UI can currently give me that.
Every OS upgrade has brought less usability at the expense of 'looking nice', I hate having to go through multiple screens to do something as simple as turn on bluetooth and start a media player, one click for me and it's done. Same for many things.
Click to expand...
Click to collapse
I particularly like Spb Mobile Shell. But if you've got something that works better for you than it does, I'd be interested to know what that might be. Can you tell me what makes your WinMo 6.x work so well for you?
FWIW I've never tried Android and don't anticipate doing so for quite awhile. Same for Windows Phone. I have too much invested in Windows Mobile Apps to move off it, especially since they do what I need them to do so well.
I came from using the original HTC Touch for nearly 4 years with WM6.5 and promptly went to try Android when I first got my HD2. The 2 most important thing to me on my phone is the email client and the web browsing. I couldn't get used to the native email app or K9 in Android and came back to WM6.5 for about a week.
I then took the dive to go to WP7 Mango and I love the email integration there. The web browsing is not very nice and Microsoft pushing the use of Bing is very frustrating, but the browser itself is decent. So while the battery life is absolutely horrible in WP7, it can still get me through the day on light usage.
So, I tried coming back to WM6.5 but there certainly are many things to like about the current generation operating systems. WM6.5 just feels sluggish comparatively because everything seems several more clicks away for me. There are various things I miss though. Apps I had purchased are a big one, but I can live without it for now. The other is the task manager. The automatic task management concept is a nice idea in Android but I like quick access and control over it (something ICS possibly has addressed). WP7 its not an issue for now because non-native apps don't run in the background.
Overall, I think you at least owe yourself to try Android since it can run alongside WM6.5. Give it a real shot because there are only going to be more and more things that are available to current gen OS that won't be ported to WM6.5
Tref said:
I particularly like Spb Mobile Shell. But if you've got something that works better for you than it does, I'd be interested to know what that might be. Can you tell me what makes your WinMo 6.x work so well for you?
FWIW I've never tried Android and don't anticipate doing so for quite awhile. Same for Windows Phone. I have too much invested in Windows Mobile Apps to move off it, especially since they do what I need them to do so well.
Click to expand...
Click to collapse
I guess that to me the essence of these new OS, and SPB Mobile Shell is that it puts form over function, to perform any action with those requires a lot more effort than it does with how I've set my phone up, it also seems to work slower.
For a start, I have on my Today Screen the things which I want to use or see most often. SPB Diary, easy today launcher, and alarmToday. I also use wkTask task manager for the tabs. My two soft keys are also customised, one runs WM5NewMenu (which is also run by long hold of the send key), the other runs a script I made with mortscript which closes all open programs, and resets the system settings to my default preferences, such as screen orientation and brightness.
In my WM5NewMenu popup menu, I have shortcuts to all the other things I use most frequently, such as messaging, not to open my inbox, but to open a text or email with the person I'm sending it to pre-defined. So for example if I want to text my wife, it's only 3 clicks from any screen. Note that WM5NewMenu is as quick as pressing right click with your mouse on your desktop, and each submenu is just as quick. I also backup my PIM data every day automatically have a script which sends it via email to myself, so if I have lose my phone or have to hard reset and my storage card get corrupted (or any other worst case scenario) I'll never be without the information I really need.
I also have google mobile in the launch menu, a couple of scripts to start/stop my media player, which will turn on bluetooth, allow me to connect my headset, then set the volume to maximum, offer a playlist selection and then lock the screen etc.
There are quick links to toggle WiFi and BlueTooth and start menu (the hardware buttons are too low for one handed use). I have one which opens my file explorer (apparently missing on WM7) to my IE favourites folder, and after I pick one it will close the file explorer again.
My lock screen is customised with the slider exactly where I find it the most comfortable to use, and the message is my phone number, in a different font, so I can show people easily when they ask and I've forgotten it.
A few other things without dragging on forever -
A Script which programs my work schedule into my diary with as little as 2 clicks for each day's work.
And I don't profess anything but a superficail knowledge of other OS, but the ability to use the same .LNKs and parameters as on my PC is extremely useful. For example, I can make a .LNK to the messaging .EXE, and include any or all of the following, To, CC, BCC, Subject, Content, and attatchments. Examples of use can be if you text the same thing each day, like 'I'm on my way home' would take a maximum of four clicks to send from any screen.
A coreplayer link which also sets the sreen brightness to max.
A lot of my .LNKs have different icons to the default program's
I've removed as much of the HTC customisations as I could find out how to, such as the HTC messaging.
I have a basic keylogging system in place (not a true keylogger, but it logs every time I use any program) so I can check when I did things. This sounds really anal or obsessive but, for example, it's usefull for when I take a break at work and forget when I started my lunch hour, I can just check what time I turned my phone on.
---------- Post added at 11:32 AM ---------- Previous post was at 11:23 AM ----------
Gastaroll said:
I tried American Android on my HTC HD2. Battery life on all android sucks, so I am back on WM6.5. I am very sad Microsoft switched to WP7 after 6.5 is so cool.
Android must take care of battery management before releasing OS as now it just ruins the pleasure of Android OS. My WinMo6.5 lasts more than 4 days on one charge. I wanna see Android doing this
Click to expand...
Click to collapse
I have an external battery charger and have often managed to deplete one battery before the other has been charged, but this is while watching a film with a bluetooth headset and the screen brightness at maximum.
Tried Android on HD2 & native device, HD2 soon went back to WM6.5.3 because:
-Better battery life & charging control
-Customization of WM is unbeatable
-Every icon, position, text, background can be what I want
-Fast access to all daily tasks (wifi,tethering,BT,SIM switching,email) all handled within 1 or 2 touches & all status easily viewable
-Better Asian language support
-Better Language suite applications
-Better Office applications
-Excellent Video & music players.
-OS file system is easily handled & integrates & shares better with my Notebook files.
-Stability of my WM custom rom is faultless & backup/contact/file integration to Windows applications I use are not wanting replacing due to cost & time of setup.
bbobeckyj said:
...
A coreplayer link which also sets the sreen brightness to max.
....
Click to expand...
Click to collapse
How do you do that? I haven't checked, but does Coreplayer have command line options that will allow you to start with max screen brightness?
Tref said:
How do you do that? I haven't checked, but does Coreplayer have command line options that will allow you to start with max screen brightness?
Click to expand...
Click to collapse
mortscript.
I thought that might be it. I haven't messed with mortscript for a couple of phones now. I once wrote a long script I used to report on calls, minutes and data, but it's been awhile.
Thanks
u can always boot Android from SD card and be certain that it won't mess up your WM...i've successfully ported gingerbread, froyo, honeycomb and ics on my HD2 and i'm very satisfied...have fun!
though, NAND versions are faster, more stable and have better development
no , but we wish that we can boot wm6.5 from nand / dual boot winmo and android like wph7 and android in that way maybe we boot winmo because i miss some apps there
..
When I able to do this from my HD2 on android will switch on it until then wm 6.5 is my love hehe. Stupid microsoft and metro sh...t!!!!!!!!
Do not want to miss my tethered sync with Outlook
rabilancia said:
After being an exclusive Windows Mobile user from the Pocket PC days in 2001, I tried Android on my HTC HD2 with great fear and trepidation. After 2 months i am VERY satisfied with Android and can't imagine ever going back.
Good luck with your decision.
Click to expand...
Click to collapse
I keep with WinMo6.5 because I want to do everything locally. I just don't like the buzz about putting everything on third party servers and airtime communications.
My mails are on my own servers and those of my company. When I sync my mails& contacts I use only my own electrons flowing through my private USB cables.
Neither Apple, nor Google, nor Microsoft need to know what I am doing, who i have as contacts and where I curently am located.
Additionally I am traveling frequently abroad and don't want to pay horrid sums per MByte on roaming fees.
I don't like androids behavior to start applications without asking me and there is no way to stop that, so I will keep using WM. Suck it android!
Yes and No
I got my phone in July 2010 and loved it. Battery life was bad and a lot of tweaks had to be done (thanks XDA). I got the courage to flash a custom WinMo rom by November 2010. Heard so many things about Android and tried it in 2011 and hated it. It was still shabby with Gingerbread and I missed Microsoft Office on the phone and exchange services. I ran back to WinMo after some days and didn't look back.
The world seemed to pass by and with no interest in Winmo, app development ceased (except here). WP7/7.5/8 just looked like a giant leap backwards and never tickled my fancy. Blackberry was a no. Iphone seemed overpriced. Ubuntu not out yet. That left Android, the most like the WinMo we all love. I don't like being stuck in the past, and my phone will be changed as soon as I see a decent one. The great phones now are all android. Why not seize the opportunity the HD2 afforded us to try everything?
Feb 2013, I flashed Android on NAND with Jelly Bean 4.1.2. It really has matured as an OS and I found out the best things about my Winmo UI are almost all incorporated into the ROM without much modding/tweaking. Since then, I have been happy with the phone. It can once again do things 95% percent of phones can't do. Battery life is still bad, thanks to Google syncing the lives of millions needlessly.
I really prefer avoiding storing personal information on Google servers like someone noted. There should always be options for offline methods as a backup. Maybe I am getting old and should follow the trend?
This ended up quite long, but bottom line is Android on my HD2 is a necessary step in the evolution of technology for me. Thank you and God bless.
Hi all,
Hope I'm posting this in the right place. If not, please move.
I have Remix_OS_for_PC_Android_M_64bit_B2016072603 installed as a virtual guest in Virtualbox 5.0.24_Ubuntu r1083 with Xubuntu-core 16.04 as the host machine. Using a Toshiba Satellite Pro L510. Took me four days to nut out how to get to this point, but installed and booting and stable now.
My issues:
1/ Location: When I try to run an app from Play Store it thinks I'm outside of Australia/New Zealand (the app I'm trying to run is specific to those regions). I'm in Australia, the app works fine on my phone (am logging in exactly the same way).
(* Update: I installed GPS Status and it tells me GPS is not switched on. Was hoping to then change the location with Fake GPS, which I also installed. It won't do anything with same message: GPS not enabled or similar.)
2/ Resolution: The screen defaults to portrait, as expected I suppose, but I have a 1366x768 monitor and it doesn't fit in the screen. Consequently, I have a scroll bar because as Virtualbox Guest Additions is not compatible with Remix OS at this point there is no mouse integration (I need to hit Right Control to use mouse in host and same to use in guest again). I need to press a bunch of keys to just scroll the screen up and get back to where I was going. :|
Other than that, all working great, Remix OS is great, thanks to the team that created it. The main reason I was wanting to use it is to use this one app on my computer (AFL Live) and plug my computer into the TV. I don't use my phone for anything other than that one app, SMS and the occasional call so I am by no means an Android junky. In fact, before this, I knew very little about it (but a lot about Linux/Ubuntu).
This install has been a quest, a learning curve, and these are my last two hurdles so I'm calling for help if it's out there. Trawled the net, tried some things, but have hit a brick wall with these two problems.
My first post so not sure of the protocol. If these two issues should be the subject of two separate threads, mods please advise and I will edit accordingly and create a new thread.
Tnx in advance.
(* Further update: Just having a read of this: http://forum.xda-developers.com/remix/remix-os/remix-os-installation-rooting-t3293769
Wondering if rooting the device would allow me to change any of these, in particularly, the location to Australia where it should be, or switch on GPS so my app can see where I actually am. I'm presuming it thinks I am in the Cocos Islands or somewhere else!)
(* And further update: The screen resolution was as easy as typing Alt+F1 to launch a terminal then 'wm size 1366x768'. That looked terrible, though, so changed it to 1048x768 (from memory) and it is good enough, though not perfect. I may be able to get closer with further tweaking. Now the last, and most important, hurdle to leap: How do I get Remix OS, and more specifically my AFL app, to know I'm in Australia. Frustration. It's taken about ten days, on and off, to get here and still not quite where I want to be, but hopefully my travails can help someone else along the way ...)
Gave up on it. If anyone comes up with a way of running Remix OS in Virtualbox and setting the location, please post. Guestadditions would probably fix it and maybe one day ROS will be compatible with it.
On the other hand, I did learn a lot more about Android than I cared to know, but am now thinking about buying my first ever Android tablet to do the job with a USB/HDMI adapter.
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.