Hi all!
Development Site is here for the project:
https://wiki.ubuntu.com/Touch/Devices/spyder
This release is not nearly ready for daily use,as It's just a preview like on the Nexus devices.It just got ported.
WHAT (Should) WORK:
1.Display
2.Touch
3.Wifi
4.Sound
5.SMS
6.Camera (for pictures,not sure about video) .
7.Calls (not for everybody i guess...) .
WHAT DOESN'T WORK:
1.There's so much that is still being implemented into the Touch version of Ubuntu, that this list could get pretty long.
2.Cellular data - Ubuntu Touch Issue
3.Almost no sensors support other than touchscreen work so no rotation so on - Ubuntu Touch issue.
4.No HD codecs (still being worked on) Ubuntu Touch issue.
5.No screen timeout / auto blank -- be careful when walking away from the device.
6.Need to press the power button to turn the screen off. Ubuntu Touch issue.
7.Many Random Issues.
So let's begin the tutorial :
1.Download the latest Motorola Razr lunch files for Ubuntu Touch and place it on you device memory.
LINK: XT910:http://goo.im/devs/Hashcode/umts_spyder/ubuntu-phablet
XT912:http://goo.im/devs/Hashcode/spyder/ubuntu-phablet
2.Download the Ubuntu Touch Preview File System and place it on your device memory:
LINKS:
Part 1:http://d-h.st/I0E
Part 2:http://d-h.st/SQT
If you don't know how to extract from two parts rar just place the two parts in the same folder and extract the first rar , That's all.
3.Reboot into Safestrap (Please report if you were able to boot Ubuntu Touch Using Boot Menu Manager).
And create a new rom slot in slot number 4 with the 2GB data option (IT WON'T WORK WITH 1GB DATA PARTITION).
4.Install the raring-preinstalled-phablet-armhf.zip FIRST,and then the phablet-2013xxxx.zip SECOND.
5.Thats it,enloy .
Credits:
STS-Team (Hascode and Dhacker29) BIG THANKS FROM THE RAZR COMMUNITY!
Some Q&A:
Q.What kernal should i run?
A.Any kernal,since It's kexec based.Tested on ICS kernal and JB Kernal (Both tested by me).
Q.Does this work on BMM?
A.Not that I or anybody know,let us know if you succeed run it on BMM.
Q.Why Softkeys are not working?
A.Ubuntu Touch is based on Touchscreen experience only,no hardware buttons,this is why.
Screenshots:
http://razreeu.files.wordpress.com/2013/03/p1000882.jpg
http://razreeu.files.wordpress.com/2013/03/p1000883.jpg
http://razreeu.files.wordpress.com/2013/03/p1000877.jpg
http://razreeu.files.wordpress.com/2013/03/p1000878.jpg
http://razreeu.files.wordpress.com/2013/03/p1000879.jpg
http://razreeu.files.wordpress.com/2013/03/p1000880.jpg
http://razreeu.files.wordpress.com/2013/03/p1000881.jpg
http://razreeu.files.wordpress.com/2013/03/p1000864.jpg
(Thanks hwhitewolf!).
This is it .
I tested it, it works as it's suposed to (W.I.P.). It can be very fun to play with, and remember, it does't have boot animation and the screen doesn't lock by itself, you have to press power button to lock it. A big thanks to DanielMod! And the Ubuntu community!
Awesome, will test it when I get home, really excited about this. :thumbup:
Sent from my XT910 using Tapatalk 2
Just want to know if we can install it in slot 2 BMM ? Great work
I by myself couldn't install this on BMM,Would be nice if someone would success doing so.
Thanks, working very well for a preview, I'll keep following for updates.
---------------
XT910 - Brasil
couillu44 said:
Just want to know if we can install it in slot 2 BMM ? Great work
Click to expand...
Click to collapse
No, only Slot-4 in safestrap as far as I know.
ICS KERNEL only?
Cracked the screen on my Razr, and got a Note 2 a few months ago, downloading this now. Been wanting to try it, just not on my every day phone!
Edit: Ehhh... Maybe not. The phone won't power up after sitting in a drawer for a couple months. I guess it's mad at me.
jancarlos1597 said:
ICS KERNEL only?
Click to expand...
Click to collapse
I only tested it on ICS kernel, so I don't know if it works in another kernel.
I want to try that two.
I Can't get It to work on BMM,any tip on how to convert my system to SS?
DanielMod said:
I want to try that two.
I Can't get It to work on BMM,any tip on how to convert my system to SS?
Click to expand...
Click to collapse
You dont't have to convert it, what ROM are you on? Probably you just have to uninstall BMM and install SS instead.
On Latest CM10.1,Woundering if someone tried...
EDIT:
Yes...never try that on your phone,i had a problem i guess with BMM so now i need to restore ICS...at least no more CID errors
DanielMod said:
On Latest CM10.1,Woundering if someone tried...
EDIT:
Yes...never try that on your phone,i had a problem i guess with BMM so now i need to restore ICS...at least no more CID errors
Click to expand...
Click to collapse
Now you can install SS.
As I did,It worked too slow,It's a really beta segment,didn't liked the system so much but lets see how It's being developed
DanielMod said:
As I did,It worked too slow,It's a really beta segment,didn't liked the system so much but lets see how It's being developed
Click to expand...
Click to collapse
In my razr this isnt work... :\
Stock: ics
slot 1: aokp JB4.2.2
slot 4: Ubuntu touch
The OS is starting up, but only the power button woks (sleep, and power off). No touch, no hwbuttons. :\ If i plug it into monitor with hdmi, there is no reation... Unusable. Any idea? (rebooted, 2times)
What is supposed to work?
I can boot and gets to what I think is either home screen or lock screen.. but after that I can do nothing..
seems like touch doesnt work?
Can turn on and off the screen and turn off the phone.. thats it?
tugge said:
What is supposed to work?
I can boot and gets to what I think is either home screen or lock screen.. but after that I can do nothing..
seems like touch doesnt work?
Can turn on and off the screen and turn off the phone.. thats it?
Click to expand...
Click to collapse
I don't know what's going on with you, guys. When I used it, I used twitter, facebook, internet browsing, messaging, wifi, touchscreen worked fine, I took pictures, made calls. Data didn't work, but that was expected.
Try flashing the 14/03 version of the phablet archive and see what happens.
I could bring up the dialer, but when I hit the call button, nothing happens. Cant seem to find a place to sign into accounts, and the soft keys don't work.
One thing for sure, though... I am excited to see a stable release. As long as it has tether, it'll be my daily driver for sure.
Anyone got this working in jb yet? I tried all releases and I have no touchscreen with all of them.
Sent from my DROID RAZR using xda premium
Related
Shortly after Team DRH's last update for their ICS 1.2 I installed it no problem and it ran for a few weeks. Then I left the tablet alone for a week or so and when I turn it on now the wifi is not working, it just says "turning on wifi" but never actually does. I've followed the reflash instructions here: http://forum.xda-developers.com/showpost.php?p=23147934&postcount=4 and I can re-install ICS endlessly. But even after following those instructions, and even after RayWaldos NVFlash for dummies, it still always says "turning on wifi" but doesn't.
When, during the above flashing, I let the stock tapntap boot, wifi works no problem. It's only when i install a ROM that it stops working. I even tried installing Gtabcombover and it gave me the same "turning on wifi" problem.
I did try searrching the forums, but I see no mention of this anywhere.
Thanks.
If I can be more to the point: does anyone know of a way to completely reflash stock everything? I thought I was doing that, but obviously not enough.
Or do I need to crack open my case and push that Dirty Little reset button?
Slightly Askew said:
If I can be more to the point: does anyone know of a way to completely reflash stock everything? I thought I was doing that, but obviously not enough.
Or do I need to crack open my case and push that Dirty Little reset button?
Click to expand...
Click to collapse
I was able to use the DHR NUFLASH.. It worked real well for me.. download the right file (bootloader 1.1 or 1.2) to your pc, for your g-tab.hook up your USB cable Turn on your tab wile holding your volume (-) key , the logo will come on and then go black. Then go to the nuflash- win file, you downloaded to your pc and run.. The instructions are on the DHR site are vary good I read them a few times before I tried. Its worked great for me.. I'm a noob. Lets just say its just about makes the gtab un-brickable...
Sent from my G Harmony v2.8 using xda app-developers app
graftonrod said:
I was able to use the DHR NUFLASH. . .
Click to expand...
Click to collapse
Well the good news is that after reading your post I went straight to the DRH website and lo and behold they had just posted Beta 1.3 that morning. I redownloaded their Full Stock CWM 5504 NVFLASh file even though I already had it, and the Beta 1.3.
I flashed the stock file and let it boot just like they said but the setup process began a FC loop and would not complete. I simply rebooted and the setup was able to complete. The I installed the Beta 1.3 with no Gapps and it worked like a charm. Wifi was working and everything, except there was no Market. So I did a wipe/FR and installed again this time with Gapps and everything is back, wifi, market, all good. And I have noticed that it all seems to work a ton faster and smoother.
I would like to disable the buttons on the side of the device, and have stumbled on this post.
http://forum.xda-developers.com/showthread.php?t=1191699
I have tried it, but it didn’t work.
Is there a similar way for CM10 A5 ?
mpps1970 said:
I would like to disable the buttons on the side of the device, and have stumbled on this post.
http://forum.xda-developers.com/showthread.php?t=1191699
I have tried it, but it didn’t work.
Is there a similar way for CM10 A5 ?
Click to expand...
Click to collapse
At last I managed to setup again a decent development environment, so I've recompiled the last available kernel from DerArtem's github, taking out the foliocap part. I've tested it in my Folio and seems working. It's a boot.img flashable with fastboot from a PC with command:
Code:
fastboot -u -S 0 flash linux boot.img
The side buttons light up but do nothing. Even my Folio is affected by that crazy buttons behaviour from day one, so I think it's hardware failure (every ROM from stock till this marvelous CM 10 is affected).
Again MANY thanks to DerArtem who took our tablet to its true level.
Thanks! I will test it at weekend...
it is possible to do the same for CM10.1 (4.2.2) Alpha 1
thanks
jovial said:
it is possible to do the same for CM10.1 (4.2.2) Alpha 1
thanks
Click to expand...
Click to collapse
Recompiled the latest kernel from Artem's github without capacitive buttons, I can't test it (still on 4.1.2 waiting for an SD card to update it), let me know if it's OK.
boot.img
thanks
it's work
Hello ppl i could really use your help.
About a few weaks ago i installed a nightly version of cm 10.2 all was working fine until my phone didnt wake up at some point. So i tried to reboot phone with holding down power button until the 3 buttons start flashing but it didnt work out my phone didnt reboot. So i tried to do it again with holding down power button but now the 3 buttons didnt start flashing but the power led went of for a second and came back up so i waited after that. my phones screen stayed black for like 15 minutes and after that the htc quitly brilliant screen comes up. When i wait another 15 minutes it will start to boot into cm.
Now i get the following problems: Sound on my phone doesnt work anymore, Camera doenst work, Cant play videos, Gps doesnt work etc etc.
I tried to install stable version of cm 10.1 flashed new boot.img but didnt seem to solve the problem same problems as with 10.2 remain.
does anyone know how i can fix this?
Still didnt fix my problems does anyone know what to do?
Tried different roms with different kernels but booting still takes awfull long.
Also i still have that sound, camera, video and many other system features dont work.
Plz help me
Roodenburgertje said:
Still didnt fix my problems does anyone know what to do?
Tried different roms with different kernels but booting still takes awfull long.
Also i still have that sound, camera, video and many other system features dont work.
Plz help me
Click to expand...
Click to collapse
Try wiping all the partitions I mean full wipe dalvik+system+cache+data and install the ROM again .....
Have you tried it already....?????
Sent from my HTC One X+
Does the camera not work at all or just not with the normal app?
[email protected] said:
Try wiping all the partitions I mean full wipe dalvik+system+cache+data and install the ROM again .....
Have you tried it already....?????
Sent from my HTC One X+
Click to expand...
Click to collapse
Yup also tried that but didnt help...
Maybe i must try format the /boot partition first? and flash kernel after that?
Because i think my problem is a kernel problem...
Hello partners!!!
Here we share the functional rom last for our MaX2!
At the request of many colleagues, I created this CM13 based on 29 September.
And adding the entire S19 firmware to have it fully updated and upgraded.
Fully functional quick and steady myself I was surprised with the performance tests ... 143,000 AnTuTu with hot enough to test mobile Cold believe can draw record numbers ...
To say that I still have problems with slow motion ....
I'm starting to not know where mistakes can be ....
Libs I managed to trace the entire structure of the official EUI and still does not work ....
Permits revised from top to bottom ...
Libs mother and CM13 ... zilch ...
Perhaps there may be something in the kernel (boot) but there are limited ...
As I change anything to do directly test the ROM does not start or comes into infinite loops ....
So ... I leave the rom completely finished but with 2 bugs.
And each user knows what he wants or what you need.
But the ROM is fully functional for day to day and is really fast and stable.
BUGS:
1 Slowmotion nonfunctional. The rest of the camera is fully functional with 21mpxl.
2nd nonfunctional IRDA. (With this ... if not roms stocks moment ... little we can do ...)
The first!!!! IMPORTANT
We do not force anyone has use or install the rom.
We do not make yourself responsible for possible errors or brik the terminal.
We simply share our work for all so that we can have the terminal in our language.
RoM CM13
CM13 based official of the day 29/09/2016
s19 official firmware with all its libs + kernel.
Rom eliminated completely stock only apks that created conflict with our terminal.
Doze functional.
Sound perfect.
wiffi
BT
Integrated Pico gapps
Some improvements in the build.prop
Installation Method
We have created a zip FULL.
ROM contains firmware s19 + recovery + 5.8 everything necessary for you to come firmware do not have problems to come and stay all properly installed and running smoothly or silly scares.
* Download rom.
* Enter the zip rom on your terminal.
* Restart recovery.
* Since the recovery to the wipes.
* Once the wipes, select the zip and install.
* Once installation is complete, restart System.
* Wait for the rom you first start, it takes a few minutes not alarmed.
downloads TeaMSpaiN
CM13 ROM S19: https://mega.nz/#!SwIHSB7C!rFQJsQxx-J-RI121GWsaC6DAhDkLHzJdDPvdVabZRRY
Your comments on this rom.
And if you find any bug report to try to fix them.
Greetings comrades!
DONATE PAYPAL: https://www.paypal.me/ParasiteYgaseOso
thanks for sharing this
Sent from my Le X821 using XDA-Developers mobile app
Thank you! I will try this rom.
Changing action of the left hardware button doesnt work, it just keeps working as "menu" button.
ArctiX said:
Changing action of the left hardware button doesnt work, it just keeps working as "menu" button.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=68885350&postcount=235
meangreenie said:
http://forum.xda-developers.com/showpost.php?p=68885350&postcount=235
Click to expand...
Click to collapse
Thanks, that worked
Thanks for your work! Does Camera API 2 work this time?
I flashed this rom today. Everything works well for me!
wiped system and dirty flashed from previous cm13 and it seems to be running very well
Nice, smooth, we will see battery performance compared to Mokee.
- Camera2 api doesnt work
- Slowmotion doesnt work
- IR doesnt work
- For me, missing Aegis app from Mokee is a big step back
Sent from my Le X820 using Tapatalk
@ParasiTe_RemiX Did you build this from source or port from another device?
Beautiful ROM, but for me in Japan for some reason LTE is not working, I can get only HSPA. This is strange because in the stock eui I can use LTE no problem.
Also the hardware buttons light up when you touch the screen, on Eui they only lit up when you touched the buttons, not the screen.
Oh, and after checking now, the AudioFX doesn't work system wide, only in the cm music app, in e.g. YouTube or Tidal, it doesn't make any change in sound.
Notification light is blinking when charging, is there any way to make it always on and not blinking?
ArctiX said:
Also the hardware buttons light up when you touch the screen, on Eui they only lit up when you touched the buttons, not the screen.
Oh, and after checking now, the AudioFX doesn't work system wide, only in the cm music app, in e.g. YouTube or Tidal, it doesn't make any change in sound.
Notification light is blinking when charging, is there any way to make it always on and not blinking?
Click to expand...
Click to collapse
For the hardware buttons backlight, you can turn them off in settings/buttons or you can turn the brightness of them right down, via editing the max_brightness file.(can't remember the path name atm, but can easily google)
For the charging light, you can turn the charging light off in settings/display. The options for them don't seem to work unfortunately.
When I plugged my phone to the computer I noticed a blank file with no name and hard disk icon on my sd card, when I tried to delete it, it wiped my whole sd card! don't delete that file if you see it.
Hello, This ROM is also compatible with the version Le Max 2 Pro?
pickmod said:
Hello, This ROM is also compatible with the version Le Max 2 Pro?
Click to expand...
Click to collapse
No, you can't flash it for X620!
bahuy2003 said:
No, you can't flash it for X620!
Click to expand...
Click to collapse
I have Le Max 2 Pro X820... it is compatible?
Thank you, looks really production quality
This is extremely close to what I wanted from this device: Straighforward CM13 (ok, I'll want CM14 next), no bloat, functional and fast.
Also rooted, which means I control my device, not some vendor who wanted my money but fails to cede the control over what he sold.
And most importantly: No longer any of these Chinese apps, which refused to get uninstalled while they claimed about any privilege Android can provide.
I sure hope security patches will be coming for years as the device looks powerful enough to last a long time.
Only bug I've found so far is apps like Hangouts and Duo can't access the Camera for video calls. Apart from that, flawless so far.
Hello!
Is it possible to install Lineage OS 14 on Xperia Mini pro?
If not, what is the latest Lineage OS version that is possible to install on Xperia Mini Pro?
Henrik Jansson said:
Hello!
Is it possible to install Lineage OS 14 on Xperia Mini pro?
If not, what is the latest Lineage OS version that is possible to install on Xperia Mini Pro?
Click to expand...
Click to collapse
CM12.1 (based on Android 5.1.1) should be the latest CM (or LOS) that Xperia Mini Pro support.
Ok, thanks!
Do you know where to download it, and if there is some step by step instruction somewhere on the internet how to install it.
Henrik Jansson said:
Ok, thanks!
Do you know where to download it, and if there is some step by step instruction somewhere on the internet how to install it.
Click to expand...
Click to collapse
Please head over to the DEV forum of this device. The thread is located the top several.
Sent from my D6503 using XDA Labs
Ok, where can I find "DEV forum"?
Xperia Mini, Mini Pro, Xperia Pro, Active, Live with Walkman Android Development
in legacy xperia you can download CM13 (android M). I´ve installed it in my xperia mini pro (mi only phone) and it´s enought stable for me to use it.
in my opinion, works much better than cm11
https://basketbuild.com/devs/AdrianDC/LegacyXperia/mango/LineageOS-14.x
How to install LineageOS 14.1 Rom (Android 7.1.2)
1. External memory card is required to install the rom (Ext4 only 1 partition). At least around 4gb, must be very fast (Class 10 u3), and should be at around 8gb if possible. All apps, data, etc will go here.
2. Flash boot.img (In fastboot mode).
3. Go wipe, swipe. Go advanced wipe and wipe system.
4. Go advanced --> sideload. Connect USB and type 'adb sideload rom-14.1-xxx.zip' & after type 'adb sideload opengapps-7.1-xxx.zip'
5. Reboot to system. Ignore any warning message.
Thanks for the mango link, but where is the boot. Img file ?
babaorum1973 said:
Thanks for the mango link, but where is the boot. Img file ?
Click to expand...
Click to collapse
Did you take a look inside lineage-14.1-20170514-UNOFFICIAL-LegacyXperia-mango.zip ?
Because I didn't test it yet: Are there any issues with this build (camera working)?
Just tried lineage-14.1-20170514-UNOFFICIAL-LegacyXperia-mango.zip and the installation overall was like described by Tromponauta.
The problem is that the touch screen is not responding within LOS. Everything else works (keyboard, camera etc.), just the touch screen seems to have problems. It works just fine inside TWRP and booting LOS for the first time it was responding for the first moment and then stopped (no response, like a frozen OS but the hardware keys still work). I've rebooted back inside TWRP to confirm the touch screen is working and it is.
Any ideas?
saljut7 said:
Just tried lineage-14.1-20170514-UNOFFICIAL-LegacyXperia-mango.zip and the installation overall was like described by Tromponauta.
The problem is that the touch screen is not responding within LOS. Everything else works (keyboard, camera etc.), just the touch screen seems to have problems. It works just fine inside TWRP and booting LOS for the first time it was responding for the first moment and then stopped (no response, like a frozen OS but the hardware keys still work). I've rebooted back inside TWRP to confirm the touch screen is working and it is.
Any ideas?
Click to expand...
Click to collapse
There was a problem with my display cable. Changed the display and it works just fine now.
Just energy consumption seems to be very high. I bought a new battery which is listed as 100% for around 3hours and then drops down to 0% immediately.
saljut7 said:
Just energy consumption seems to be very high. I bought a new battery which is listed as 100% for around 3hours and then drops down to 0% immediately.
Click to expand...
Click to collapse
This problem is caused whenever a SIM card is inserted. Without SIM card the battery lasts a day as expected.
saljut7 said:
This problem is caused whenever a SIM card is inserted. Without SIM card the battery lasts a day as expected.
Click to expand...
Click to collapse
Its probably your phone hardware problem. I'm running CM14.1 on two mango phones.. without gapps and everything works .. well.. one of them have occasional freeze problems I'm struggling to diagnose, so removing battery is required from time to time to reboot it.
Anyway sim card works fine on both phones with normal battery use.
ROM is quite fast (maybe faster then CM11) but I'm using A1 sd card and no gapps ..
btw I also had some freezing problems on this phone when on other ROMs so maybe its hardware..
Its certainly worth giving CM14.1 try (as per other post earlier on)
EvilMonkey88 said:
Its probably your phone hardware problem. I'm running CM14.1 on two mango phones.. without gapps and everything works .. well.. one of them have occasional freeze problems I'm struggling to diagnose, so removing battery is required from time to time to reboot it.
Click to expand...
Click to collapse
I've experienced this as well but I doubt this has something to do with the hardware (except the fact that the hardware is maybe just too outdated to handle a current LOS and current apps).
EvilMonkey88 said:
Anyway sim card works fine on both phones with normal battery use.
Click to expand...
Click to collapse
Is there really no effect on battery drain if the ROM was not optimized for certain country GSM settings?
EvilMonkey88 said:
ROM is quite fast (maybe faster then CM11) but I'm using A1 sd card and no gapps ..
btw I also had some freezing problems on this phone when on other ROMs so maybe its hardware..
Its certainly worth giving CM14.1 try (as per other post earlier on)
Click to expand...
Click to collapse
Yes, the sk17i is still a great peace of hardware for me used as "walkman" and for instant messaging. I'm very thankful that the sk17i is still suppoprted, thanks to all devs involved!
saljut7 said:
I've experienced this as well but I doubt this has something to do with the hardware (except the fact that the hardware is maybe just too outdated to handle a current LOS and current apps).
Is there really no effect on battery drain if the ROM was not optimized for certain country GSM settings?
Yes, the sk17i is still a great peace of hardware for me used as "walkman" and for instant messaging. I'm very thankful that the sk17i is still suppoprted, thanks to all devs involved!
Click to expand...
Click to collapse
On main mango I get between 12-18 hours depending on use.. (its mostly light though.. messengers, emails, phone calls, etc not much browsing) so battery drain is same ish as other ROMs I tried..
2nd mango with CM14.1 works as alarm clock and sometimes squeezebox controller. mostly on airplane mode which gives over week battery life.. (no sim on that one)
3rd mango is on stock gingerbread converted into dashcam .. I get about 6-7 hours battery with HD recording on Daily Voyager (had to use tasker to turn off screen during recording though)
Got two more of those little buggers but sadly as spares now.. (broken screens)
Everyone tells me I'm mad to still use mini pro.. but I really like small phone with great keyboard.. (by today standards I should say tiny phone lol)
Once a while I consider buying new phone but haven't actually done it yet lol
Yes! +1 Thank you devs for all your work on xperia phones!.. Cheers
p.s I'm still hopeful for Android Go one day
Awesome... well I sitll doubt that my battery drain has something to do with the hardware. As far as I remember the battery life was already not very good when I was using the original Android for 2-3 years. My current battery is now at least 5 years old so I think the current battery capacity is quite okay. Before I had a Motorola xt894 with a Cyanogen Mod experimental/snapshot and the battery life was horrible in comparison to the standard Rom so I think it has something to do with a not optimized LOS.
btw: Did you experience any Wifi issues connecting to public Hotspots? Sometimes I have the problem that I can not connect to public hotspots that worked yesterday. The Wifi list says "saved" to the specific Hotspot after I tried to connect (insteadt of "connected").
saljut7 said:
I've experienced this as well but I doubt this has something to do with the hardware (except the fact that the hardware is maybe just too outdated to handle a current LOS and current apps).
Is there really no effect on battery drain if the ROM was not optimized for certain country GSM settings?
Yes, the sk17i is still a great peace of hardware for me used as "walkman" and for instant messaging. I'm very thankful that the sk17i is still suppoprted, thanks to all devs involved!
Click to expand...
Click to collapse
saljut7 said:
Awesome... well I sitll doubt that my battery drain has something to do with the hardware. As far as I remember the battery life was already not very good when I was using the original Android for 2-3 years. My current battery is now at least 5 years old so I think the current battery capacity is quite okay. Before I had a Motorola xt894 with a Cyanogen Mod experimental/snapshot and the battery life was horrible in comparison to the standard Rom so I think it has something to do with a not optimized LOS.
btw: Did you experience any Wifi issues connecting to public Hotspots? Sometimes I have the problem that I can not connect to public hotspots that worked yesterday. The Wifi list says "saved" to the specific Hotspot after I tried to connect (insteadt of "connected").
Click to expand...
Click to collapse
hmm maybe you could try battery calibration? or "new" battery.. those are very cheap. seriously no excessive drain here on LOS.. managed 19hours and 10% left today..
no experience of public wifi problems.. but I don't really use them tbh
My main problem with LOS is random freeze when display wont wake up (even when notification is working and background menu lights).. sometimes phone is OK for few days but other times it can freeze few times a day. I keep changing settings in kernel auditor but cannot find out cause yet.. for a while I had suspicion freezes are more likely when using build in browser.. but maybe it was just coincidence
EvilMonkey88 said:
sometimes phone is OK for few days but other times it can freeze few times a day.
Click to expand...
Click to collapse
My sk17i lists errors like
System UI has stopped
com.android.phone has stopped
Settings has stopped
and is always rebooting / in a boot loop. I wanted to reinstall LOS but somehow my whole system seems to be read only. I've already tried https://forum.xda-developers.com/droid-turbo/help/accidently-selected-read-twrp-how-undo-t3312533 but everytime I access TWRP after a reboot "Mount" -> "Mount system partition read only" is checked. I tried to reinstall TWRP with
Code:
fastboot flash boot boot.img
but this doesn't affect the checked "Mount system partition read only" setting so I think TWRP is not reinstalled. Any idea how to fix this? In the end I just want to start over with a new installed LOS.
saljut7 said:
My sk17i lists errors like
System UI has stopped
com.android.phone has stopped
Settings has stopped
and is always rebooting / in a boot loop. I wanted to reinstall LOS but somehow my whole system seems to be read only. I've already tried https://forum.xda-developers.com/droid-turbo/help/accidently-selected-read-twrp-how-undo-t3312533 but everytime I access TWRP after a reboot "Mount" -> "Mount system partition read only" is checked. I tried to reinstall TWRP with
Code:
fastboot flash boot boot.img
but this doesn't affect the checked "Mount system partition read only" setting so I think TWRP is not reinstalled. Any idea how to fix this? In the end I just want to start over with a new installed LOS.
Click to expand...
Click to collapse
Hmm not sure what to suggest as haven't experienced this. In my case everything went smooth on 3 different phones (sk17i) when following instructions from other post:
https://basketbuild.com/devs/AdrianD...LineageOS-14.x
How to install LineageOS 14.1 Rom (Android 7.1.2)
1. External memory card is required to install the rom (Ext4 only 1 partition). At least around 4gb, must be very fast (Class 10 u3), and should be at around 8gb if possible. All apps, data, etc will go here.
2. Flash boot.img (In fastboot mode).
3. Go wipe, swipe. Go advanced wipe and wipe system.
4. Go advanced --> sideload. Connect USB and type 'adb sideload rom-14.1-xxx.zip' & after type 'adb sideload opengapps-7.1-xxx.zip'
5. Reboot to system. Ignore any warning message.
Click to expand...
Click to collapse
maybe sd card is corrupted, have you tried different one..?
Try wipe plus format everything and try again?
So does sideload completes fine and then you got error and bootloop?
Out of interest what ROM have you had before?