** Work-In-Progress: Ubuntu Touch Preview is just that.. a PREVIEW. Do not complain about missing features, etc. The OS isn't nearly ready for primetime. **
Curious as to how the Ubuntu Touch Preview looks? Why not load it on your Droid 3 and see for yourself.
Instructions:
1. Make a Titanium Backup and/or backup in recovery of your current Android (or just keep it on a different slot). This preview is fun to play with but not a replacement for something as developed as CM 10.1
2. Download the Droid 3 Mini-Android base for Ubuntu Touch and place it on your device:
[03/01] http://goo.im/devs/Hashcode/solana/ubuntu-phablet/ (use the newest one)
3. Download the latest Ubuntu Touch Preview Filesystem .zip from Ubuntu:
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/quantal-preinstalled-phablet-armhf.zip
If the above link is broken, use this link for a full listing of the current build files (download the quantal-preinstalled-phablet-armhf.zip .. soon to be raring-preinstalled-phablet-armhf.zip):
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
4. Reboot into Safestrap. Create a NEW 2GB ROM in the #4 slot.
IMPORTANT:
4a. Install the quantal-preinstalled-phablet-armhf.zip FIRST, and then the phablet-2013xxxx.zip SECOND.
5. Reboot and Enjoy
FIRST BOOT TAKES A LONG TIME. AND THERE'S NO BOOT ANIMATION. BE PATIENT (MAYBE 3-4 MINUTES).
WHAT WORKS:
Display
Touch screen
Wifi
Audio
WHAT DOESN'T WORK:
There's so much that is still being implemented into the Touch version of Ubuntu, that this list could get pretty long.
Due to memory issues, the device gets VERY laggy after just a little while of use. This means the swap mem is full. I hope they work on the amount of memory used and how it's freed over time.
Barely any sensors other than touchscreen work. IE: no rotation, etc. Ubuntu WIP issue.
No HD codecs (still being worked on) Ubuntu WIP issue.
No screen timeout / auto blank -- becareful when walking away from the device. Need to press the power button to turn the screen off. Ubuntu WIP issue.
RELATED UBUNTU TOUCH LINKS:
(Some of these describe how to install it on devices -- you can ignore those instructions and follow the above)
Ubuntu Touch Wiki: https://wiki.ubuntu.com/Touch/
Release Notes: https://wiki.ubuntu.com/Touch/ReleaseNotes
IRC Channel on freenode.net: #ubuntu-touch
Re: [ROM] Ubuntu Touch Preview [02/28: Alpha Update #1]
Neat. I had to battery pull to get it to boot, bootlooped until I did. It feels like unity, for my phone. It'll be interesting to see how it performs on our device when it's complete
Sent from my XT860 using xda premium
Fine!, downloading and booting in moments! i was wondering about this in the forums, some days ago! Hash, you're the best!
Glad to see an alternative for our devices...who knows...maybe this could lead to a fully functional rom...
EDIT: Sadly, it doesn't boot at all...same issues as latest CM10.1, but after a while of black lit screen, the phone turns off...trying later something else
Re: [ROM] Ubuntu Touch Preview [02/28: Alpha Update #1]
FrankieDedo said:
Fine!, downloading and booting in moments! i was wondering about this in the forums, some days ago! Hash, you're the best!
Glad to see an alternative for our devices...who knows...maybe this could lead to a fully functional rom...
EDIT: Sadly, it doesn't boot at all...same issues as latest CM10.1, but after a while of black lit screen, the phone turns off...trying later something else
Click to expand...
Click to collapse
I had the same until I battery pulled
Sent from my DROID3 using xda premium
Looks pretty cool. I think I could get used to that interface pretty quickly. I did have a little trouble getting back into SafeStrap to boot into the stock ROM (or CM10.1 in slot1).
I used both the power button and battery pull to restart, I got the SafeStrap menu, chose boot to recovery, and in a few minutes I get the Ubuntu screen back. I finally got into SafeStrap by holding VolUp & VolDown while powering on and choosing BP Tools (bottom option).
I'll have to go back through the flash process and test a few things. Sorry that it's messing w/ some of your devices.
3/1/13 Build worked fine for me but I do have one of the older CPU's since all the kexec builds have worked for me, first boot time was only like 20 seconds and it still worked pretty quickly (but I only used it for about 10 minutes), seeing something different was refreshing and it took me about a minute to realize there was no lockscreen, most definitely a developer preview but it looks promising.Thanks Hashcode for the preview build and all the work you do, I'll keep testing them when they come out.
oh yeah the safestrap problem persisted for me as well had to hold the volume buttons to get back to Rom selection. No biggie
Hi
I tried phablet-20130301-cm_solana.zip and it worked better than I expected, I could even make calls.
The experience is quite nice and it seems Ubuntu Phone OS is very promising!
Thanks
taksan said:
Hi
I tried phablet-20130301-cm_solana.zip and it worked better than I expected, I could even make calls.
The experience is quite nice and it seems Ubuntu Phone OS is very promising!
Thanks
Click to expand...
Click to collapse
Are you on GSM?
Sent from my DROID RAZR HD using Tapatalk 2
I didn't even try calling. I didn't expect it to work
Sent from my XT860 using xda premium
Right now phone function is only implemented for GSM. The GSM RAZR has working voice calls. I didnt think D3 would work either but in theory it could.
(I occasionally activate a 3g SIM for testing, but didnt for the preview.)
Sent from my DROID RAZR HD using Tapatalk 2
taksan said:
Hi
I tried phablet-20130301-cm_solana.zip and it worked better than I expected, I could even make calls.
The experience is quite nice and it seems Ubuntu Phone OS is very promising!
Thanks
Click to expand...
Click to collapse
I tried dialing one call to one of our office lines while I was booted into Ubuntu . It dialed and rang ok but I couldn't hear the receptionist when she answered and she couldn't hear me.
Sent from my Nexus 7 using Tapatalk HD
Yes, I'm on GSM. I didn't expect it to work either, but I just thought I'd try.
The problem is that it usually doesn't boot and keeps "boot looping". The first time I pulled the battery and it worked, but now it is not working anymore.
I'm trying a reinstallation.
Even though it is quite crude, it worked better than CM10 (the droid 3 version), because the CM10 phone service crashed on start and I couldn't make
calls and neither connect to WiFi
I got it working once again, but after a while it froze. I tried rebooting the phone and it isn't booting anymore.
Ok, booted and tried, it works really well for an early alpha, who knows...this could be the base for a fully functional rom? i'm a dreamer...
Anyway i'm on GSM and calls are lagging of 1-2 rings, and voice seems to be broken, anyway, good work! as usual
Very nice! Works great for being so new. Could not do much as it would not connect to my work WiFi but expected with such an early build. Looking forward to future updates.
Being based on the CM kernel is it safe to assume we will not see any camera function for this unless it first gets worked out in the CM 10 builds?
thanks yet again Hash !
Installed as per the first post.
First boot - no longer than one min I reckon.
Wifi works, got on to FB with browser and even posted
Today showing work mate, dialled his number (without any hint of cell network / settings) and to my amazement not only did it dial, upon answering we could hear each other fine, maybe a tad lagged half a second or so but honestly worked fine!!
May have imagined things but it also appeared to get faster again after 5-10mins of being powered on, reboots no issue.
Just no idea how to power off correctly lol, seems like holding power button puts it in sleep (saw today image very dark but certainly there), then could not wake (happened yesterday also the can not wake part), so I just battery pull, again reboots no issue
Cheers
Ok man im trying to install this on my droid 3 to see how it works and then i was going to try and port ubuntu to the k1 tablet but on part 3 when installing it it will get almost done and by then my phone is very hot as well and any way it will get almost done installing and the phone will go black and i will have to pull the battery to even get the phone to do any thing so im asking what am i not doing right? I will like to get this booted on the droid 3 to get a fill of how this works befor i port to the k1 tablet.
Sent from my K1 using xda app-developers app
---------- Post added at 08:10 PM ---------- Previous post was at 07:16 PM ----------
leerpsp said:
Ok man im trying to install this on my droid 3 to see how it works and then i was going to try and port ubuntu to the k1 tablet but on part 3 when installing it it will get almost done and by then my phone is very hot as well and any way it will get almost done installing and the phone will go black and i will have to pull the battery to even get the phone to do any thing so im asking what am i not doing right? I will like to get this booted on the droid 3 to get a fill of how this works befor i port to the k1 tablet.
Sent from my K1 using xda app-developers app
Click to expand...
Click to collapse
I got it installed i had to install in slot 2 not 4 to get it all the way installed i dont know y this matters but o will any way i tested it in the other slots and it will not work in them ony 2
Sent from my K1 using xda app-developers app
Just got it from Ubuntu:
Known Issues
Power Consumption
Currently the devices can not be shutdown from within the UI or by pressing the power button. Even if you use the power button long press your battery will be drained.
To shutdown a device completely there are two options:
Remove the battery and replace it. (Not an option if battery is not removable)
Stop it from the adb shell by executing the following commands:
adb root
adb shell reboot -p
Memory Usage
Memory usage has not yet been optimized for the devices. It is possible to experience application crashes due to having too many applications open at the same time. A workaround is to close apps that are not being used.
Timezone
The timezone needs to be manually set from the command line. Valid values for timezones can be found in the /usr/share/zoneinfo/zone.tab file. Run the following commands ( specifying your own time zone choice ) with root permission to set your timezone:
Access your device through SSH
Then on the terminal connected to your device run:
echo "America/New_York" | sudo tee -a /etc/timezone
sudo dpkg-reconfigure --frontend noninteractive tzdata
Networking
The Developer Preview has support for Wi-Fi networking via the new network indicator, which supports basic Wi-Fi connections (Open, WEP and WPA Personal). It is possible to configure more advanced settings, however at this time this requires working directly with Network Manager system connection files.
The following network features are not yet included in the Developer Preview:
Airplane Mode/Wi-Fi Power Control
Advanced Settings (e.g. Hidden SSIDs, Manual IP, VPN…)
Bluetooth
Hot Spot/Tethering
Telephony
The Developer Preview currently only supports limited voice and SMS over GSM.
The following Radio technologies are not yet included in the Developer Preview:
CDMA
LTE
Airplane Mode
Settings ( eg. APN choice, 2G only, … )
Mobile data is not supported, data is available via Wi-Fi only.
These Call features are not yet supported:
Emergency Call Support ( ie. ability to dial emergency numbers without a valid SIM card ).
PIN/PUK support for locked SIMs
No SIM filesystem support
Speakerphone
These SMS features are not yet implemented:
MMS
Send error handling
Delivery Reports
leerpsp said:
Ok man im trying to install this on my droid 3 to see how it works and then i was going to try and port ubuntu to the k1 tablet but on part 3 when installing it it will get almost done and by then my phone is very hot as well and any way it will get almost done installing and the phone will go black and i will have to pull the battery to even get the phone to do any thing so im asking what am i not doing right? I will like to get this booted on the droid 3 to get a fill of how this works befor i port to the k1 tablet.
Sent from my K1 using xda app-developers app
---------- Post added at 08:10 PM ---------- Previous post was at 07:16 PM ----------
I got it installed i had to install in slot 2 not 4 to get it all the way installed i dont know y this matters but o will any way i tested it in the other slots and it will not work in them ony 2
Sent from my K1 using xda app-developers app
Click to expand...
Click to collapse
Got it working it tuck 20 m of living the phone on lmao
Sent from my K1 using xda app-developers app
Related
hey guys!
Well i was trawling the android forums and found this!
http://www.neopeek.com/viewtopic.php?t=7524
All thanks yo neopeek for the rom.
I decided to test it out on my kovsky. This coupled with I believe duckkly's kernels worked like a charm!! ill post the kernels up here too as I experimented with quite a few to see what worked best!
Battery life: 8 hours on full blast so i rekon around 11 on normal usage
Wifi: never ever ever dropped on me so far! thou it does seem to be weak in some places around my house where i usually should be getting more signals and strong at places where i get little signal :S.confusing
phone: well calls come in and stuff but sometimes ull see a black screen and cant see who's calling! :S
Bluetooth: paired with my mw600s just fine dont know about file transfer
market:works just fine a bit slow though..could be my internet speeds out here in pakistan.
Apart from that using whatsapp like a charm. facebook apps. gaaps everything works!! not a single sod to date been using it for around about 5 days or so.
Sorry for the spelling errors! big thanks goes out to neopeek and duckkly or whoever compiled those kernels !
PS: oh and the keys will freeze up as you hit around 20% battery. I simply reboot. Also terminal doesnt seem to be working. keeps crashing on me but i dont really ever use it in daily use so it seems to be pretty stable apart from these flaws. Also you'll need to reinstall quickpic from market
Also im on radio 1.16 i believe. 1.14 seemed to drop calls randomly.
please read all of neopeek's instructions before flashing ! happy flashing
can't confirm 20% battery being the point where keys stop working. for me 4 hours of uptime seems the be magic point...
i stopped restarting modules via script (how to has been explained many times in here) and simply restart. most of the time it happens when an app is running - now what good is it if you have a shortcut somewhere, but can't get there because back- and home-key isn't working?!
but yeah, neofroyo is a big step forwards. first time using android on x1 is fun!
for terminal to work you have to reinstall it just like quickpic.
i just hope we'll see some kernel-update soon. without it the whole thing is pointless.
lol truee..thanks for the terminal update. oh if u press the camera button it will take you back to your home screen. than i guess u could load the keyboard modules..annoying i never bother with it. try my combination of kernel it gives me decent battery lifee but yea its the kernel with all the problems. tried the new kernels but they dont seem to work properly
hm, which kernel-version is that?
might try if i know which it is. just had to step down from ygge-monster to ygge-turbo. monster made my touchscreen getting unprecise in left half.
thx for the update with cam-button - never bothered to press that, since camera doesn't work anyway.
yeah, new kernels suck for our device, especially since they're missing the specific battery-driver for x1. the only guy still working on x1-kernel has been silent for months, but i can see he's still at it (porting 2.6.35.7).
Just tried pressing cam-button.
Falls back to lockscreen, after unlock shows homescreen. But system is frozen and after some time reboots directly to android. But lots of stuff doesn't work, especially phone-stuff. So i have to reboot winmo anyway.
Sent from my X1i using Tapatalk
i think its the ducckly's keyboard not loaded as modules turbo verison. I believe it should be that because i remember the msm drivers werent really working properly on it
Sent from my Transformer TF101 using Tapatalk
All,
We don't have an ICS Bugs thread going on. I wanted to check with some of the people here on XDA to see if they are experiencing what I am. Currently on .213, but most of these bugs I've seen since the begining. Oh, I'm also in Canada running on 3G HSPA+. I'm stock, but rooted with safestrap installed.
1) When placing a phone call, the phone hangs up immediately (you here the disconnected beep), then retries the phone call a few seconds later (it always succeeds). I have tried this on a freshly wiped phone and found the same experience. I have also tried disabling the Assisted Dialing, but have found ikt's the same thing
2) When using Google Chrome, if there is a input box, most of the time my keyboard won't appear (I'm using Swype as my default keyboard)
3) Phone runs hot sometimes, and when it's running hot it slows down to a halt. Usually happens after a day or two without a restart
4) My photo doesn't appear in the text messaging app (worked in AOKP/CM9 on my D3, as well as it works on my gf's Nexus S)
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
podspi said:
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
Click to expand...
Click to collapse
Is your chrome working properly? Specifically the bug I mentioned in the OP...?
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
podspi said:
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
Click to expand...
Click to collapse
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
I'm in the US also running .213
I haven't noticed any bugs, its working fine for me. I do not use chrome beta so I can't comment on that. The stock is not too bad, I don't use it much anyways.
Sent from my DROID4 using xda app-developers app
danifunker said:
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Text entry works fine in both the stock browser and Opera. BTW, Opera also has hardware acceleration, which is why it never worked in any of the Frankbuilds of ICS based off the GB kernel ... So you can have your teh snappy and type with it too :laugh:
I'm on the 212 build and i can't screencap using power + volume down.
Is this fixed in 213 or am i just doing it wrong?
Also on 212 i can't control the default google music app or winamp from my bluetooth headset when the screen is off. I could do this before with the same version of the winamp app when i was back on gingerbread. I tried upgrading winamp, but that did nothing. Is there any change in 213?
Thanks ahead of time
Edit: just tried it and the volume down + power combo worked. Lol
One question, possible thought to ponder.
Are the bugs being described here really bugs of Android 4 or are they bugs in the individual app itself not being fully compatible with Android 4 yet?
Do similar bugs happen on a non-motorola device with android 4?
I'm considering flashing one of the leaks, so I'm trying to understand how you are sure these are ics bugs before I make the leap and run into issues.
Thanks.
Apologies if this constitutes hijacking the thread, if it does let me know and I"ll edit it to delete the question.
I was able to figure out bug #4, I had to login with my Google+ account again, since the update yesterday everything seems to be working fine.
Bugs 1 through 3 still exist, although I've switched off Global mode for now and put it to GSM only, it seems like the phone runs a lot cooler in this mode.
Even after updating Chrome to the final version, I'm still experiencing that text input bug. Maybe it's a Motorola issue... Can't wait for the next version of the leak!
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
podspi said:
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
Click to expand...
Click to collapse
for this reason I think there will be other leaks, ICS is supposed to handle killing processes much better than GB, however the settings seem to not be aggressive enough in 213.
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
I don't know, just had a random reboot after watching a youtube video in firefox, most likely memory related, not sure who's fault though, Motorola or Firefox. gotta root and use system tuner to change memory mgmt states.
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
That is a great idea. Though there hasn't been another leak since 213, so
Notification Bar Sticking/Wont Pull Down
I am on 212 currently, and I have noticed in 208 and 212 something that has happened only twice so far. Today, I just tried to check my notifications, and the bar will not pull down.
After a reboot it works fine, and it has only happened 2 times in the past couple weeks since the leaks first appeared.
Obviously it is a minor glitch, but just thought I'd throw it out there in case anyone else has seen it and overlooked it. :cyclops:
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
I have heard of a few others using this method successfully. If you are not using safestrap or just don't want to go this route take a look at the post link in my signature. It's a modified version of the original Droid 4 Utility and includes a script to jump from one ICS leak to another without losing data. It also flashes the GB files and the Kernel (boot.img) in one script, thus making it easier to go from one leak to another.
Regarding bugs, my wife got a razr yesterday. It wouldn't pull down the ICS update, so I just sideloaded it. We both run some of the same apps. So this gave me a chance to do side by side comparisons.The issue with some of the icons being small in the left top of the status seems to be a app issue. The chrome issue isn't present on the razr, of course there isn't a physical keyboard. Otherwise my 213 ICS seems to run great.
I found a new bug, it looks like GSM call forwarding doesn't work properly... at least it doesn't with my SIM card, I'm on Rogers in Canada.
Does Verizon support call forwarding? Does it work on there?
I have noticed in Chrome that pressing shift and then one of the symbol keys (like @) will only work if you hold the shift key.
More importantly I don't get notifications of app updates from google play. Check to see if you have any apps that need updating. Superuser had a update on July 1, dropbox yesterday and voodoo rootkeeper on June 28, I think. Anyone else?
So, now we have it. But we need to look at the new "issues" we're all facing. Because we're going to need some help.
The Good
We lost a lot of Blurr (thank ya Jesus!) We have a faster, better camera. A more optimized kernal for what seems like an OS with lighter thumbprint. Its fast! We can disable dozens of needlessly running apps/services. New gallery is beautiful.
The Bad
We lost the "Exit" button in the browser. Google+ is in everything with options defaulting to send anonymous usage and target ads based on our data. Auto sign-in/up is everywhere. Nova Launcher keeps getting killed by Android Battery life seems way off. Factory reset is pretty much a requirement. Clock app is super weird. Verizon bloat seems like an extra appendage that won't be amputated. Smart Actions is still broken.
The Ugly
The font is terrible. No amazing wallpapers added.
We have ALMOST a Nexus experience. What are you guys seeing with update, and what problems have you fixed? I'm super concerned that I can't "Exit" the browser. I don't like things running in memory.
I love the new update. I got it from the soak test early this week. I did not wipe first. My nova launcher has never been killed and phone is running perfectly for me since Tuesday. Love it!!!
Sent from my DROID4 using xda premium
I'm loving it. It's so fast and less bloatware. Browser can't "Exit" just like all JB roms on all devices. We also lost sleep mode on power menu. Good to see we still have mass storage usb mode. It's been removed in all Moto new lineups. This is the best ota update I've ever applied on my Android devices.
The Good & Ugly!
ChristianPreachr said:
So, now we have it. But we need to look at the new "issues" we're all facing. Because we're going to need some help.
The Good
We lost a lot of Blurr (thank ya Jesus!) We have a faster, better camera. A more optimized kernal for what seems like an OS with lighter thumbprint. Its fast! We can disable dozens of needlessly running apps/services. New gallery is beautiful.
The Bad
We lost the "Exit" button in the browser. Google+ is in everything with options defaulting to send anonymous usage and target ads based on our data. Auto sign-in/up is everywhere. Nova Launcher keeps getting killed by Android Battery life seems way off. Factory reset is pretty much a requirement. Clock app is super weird. Verizon bloat seems like an extra appendage that won't be amputated. Smart Actions is still broken.
The Ugly
The font is terrible. No amazing wallpapers added.
We have ALMOST a Nexus experience. What are you guys seeing with update, and what problems have you fixed? I'm super concerned that I can't "Exit" the browser. I don't like things running in memory.
Click to expand...
Click to collapse
Just last evening I checked the System Updates on my unrooted Droid 4 and there it was! Upgraded it.
Project Butter lives upto the mark. Works smooth like butter.
Font, could've done better.
The ONLY UGLY issue am facing:
My data from the network is somehow locked, or in short, not working. Visited Vodafone gallery & they checked the settings, which were fine, but still the data is not working by the network.
NEED HELP!
Please, suggest me how I can make the data work on my Droid 4!
Please!
Currently my phone is technically paralyzed because of this issue!
Nova works fine with me too.
supraket said:
Just last evening I checked the System Updates on my unrooted Droid 4 and there it was! Upgraded it.
Project Butter lives upto the mark. Works smooth like butter.
Font, could've done better.
The ONLY UGLY issue am facing:
My data from the network is somehow locked, or in short, not working. Visited Vodafone gallery & they checked the settings, which were fine, but still the data is not working by the network.
NEED HELP!
Please, suggest me how I can make the data work on my Droid 4!
Please!
Currently my phone is technically paralyzed because of this issue!
Click to expand...
Click to collapse
Vodafone is prepaid. Did you unlock the phone or buy it unlocked?
Sent from my DROID4 using xda app-developers app
I have several friends and relatives with Droid 4's and RAZR's. These Jelly Bean updates have been hit or miss with results.
-One Droid 4 was a brand new phone with date code 03/13 and HW B. This phone received the update quickly and smoothly. Operation has been perfect.
-Another Droid 4 had date code 16/12 and HW A, never rooted or modded, update failed 3 times, left the phone soft bricked, had to be SBF'd back to ICS. The new update will just not play nice with this phone, so it will need to be replaced.
-A RAZR MAXX got this update smoothly and battery life has been great, no lags or hiccups.
-A regular RAZR got this update and battery life is horrible, the phone gets hot, wiping cache and data did not fix it. No prior issues with ICS.
I'm guessing that Motorola may have used different components in different batches and some just will not run properly.
the shift button on the physical keyboard likes to stop toggling occasionaly. rebooting the phone fixes it for a while.
when it stops toggling, you have to push [shift] and [1] to make a "!", instead of [shift] and then [1].
No tether apps seem to be working
Sent from my Nexus 7 using xda app-developers app
pnwsr6 said:
No tether apps seem to be working
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The stock one works fine for me. I had to use SQL Lite to enable Wifi, but it seems to work, no problem.
Cheers,
Steve.
Morlok8k said:
the shift button on the physical keyboard likes to stop toggling occasionaly. rebooting the phone fixes it for a while.
when it stops toggling, you have to push [shift] and [1] to make a "!", instead of [shift] and then [1].
Click to expand...
Click to collapse
yes i noticed this too. it's a little annoying but i think there should be an update to the update coming out soon. right now id like to figure out how i can reflash with jb possibly using rsdlite as i did with ics but someone said flashing to ics now would brick my d4. im getting random reboots like once a day, but i think it may have something to do with my attempt at installing lbe which sent the phone into bootloop. so i want to clear it all and start from the top.. but how?
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
Morlok8k said:
the shift button on the physical keyboard likes to stop toggling occasionaly. rebooting the phone fixes it for a while.
when it stops toggling, you have to push [shift] and [1] to make a "!", instead of [shift] and then [1].
Click to expand...
Click to collapse
I heard others say the same thing. I've not noticed that yet.....yet
Sent from my DROID4 using xda app-developers app
I also have the SHIFT issue. Sometimes it works and sometimes it doesn't. I also have an issue with SMS. When I am sending a message the green arrow continually shows even though the message has already sent.
Sent from my DROID4 using xda app-developers app
pnwsr6 said:
No tether apps seem to be working
Click to expand...
Click to collapse
StevePritchard said:
The stock one works fine for me. I had to use SQL Lite to enable Wifi, but it seems to work, no problem.
Click to expand...
Click to collapse
Matter of fact, I had the phone root'ed, stock tether enabled on ICS. Unrooted the phone to get the update to install and once upgraded to JB, my tether was still working, so the upgrade did not reset the value in the SQL database.
Works brill anyhow.
/M
Morlok8k said:
the shift button on the physical keyboard likes to stop toggling occasionaly. rebooting the phone fixes it for a while.
when it stops toggling, you have to push [shift] and [1] to make a "!", instead of [shift] and then [1].
Click to expand...
Click to collapse
That is the most annoying bug there is for the JBupdate. Hope someone or MOT can fix this soon.
marlow925 said:
Matter of fact, I had the phone root'ed, stock tether enabled on ICS. Unrooted the phone to get the update to install and once upgraded to JB, my tether was still working, so the upgrade did not reset the value in the SQL database.
Works brill anyhow.
/M
Click to expand...
Click to collapse
Weird - I'm pretty certain it had reset for me during the upgrade.
My D4 had the stock rom + the Google Now hacked into it, plus the latest version of Hashcode's CM10, which I'd been using steadily since the Bluetooth bugs were fixed. (Around two weeks ago.) On the stock ROM, I'd always had issues of the phone occasionally (often) going crazy with background processes or something where it would heat up quite a bit and the battery would drain quickly. I also had intermittent Bluetooth issues with my car connection, where it often wouldn't connect, requiring a reboot or toggling BT, and it would sometimes lose the connection after a call.
Running CM, it stayed cool and had much longer battery life, and BT worked much more reliably.
Removing the Google Now hack to install the JB update wasn't going smoothly, so I ended up just using RSDLite and wiping the phone completely then installing the JB update manually (it wasn't showing yet as an OTA.) It's definitely faster, BUT...
The Shift key often doesn't work correctly, as has been mentioned here
Bluetooth is wonky again and I have to tell it over and over to pair with my car
Mobile data just stopped working yesterday, even after rebooting, until I manually turned off and on mobile data
Battery life is atrocious; it has been getting hot a lot and I'm probably getting not much more than half the battery life that I got in CM. Looking in the Battery info, Screen is usually the biggest battery user, but I always have it either set to Auto or to a very dim display. Looking at CPU usage shows nothing obvious. It's common for the battery to get to 95-100' F or higher. Right now it's behaving and only at 72' F - it must know that I'm complaining about it.
I'm hoping that we'll soon see (if we haven't already; I haven't checked yet) a CM based on the new kernel, so we get everything working but with the better battery life and such. Video was the only issue that I was still seeing with it.
supraket said:
Just last evening I checked the System Updates on my unrooted Droid 4 and there it was! Upgraded it.
My data from the network is somehow locked, or in short, not working. Visited Vodafone gallery & they checked the settings, which were fine, but still the data is not working by the network.
NEED HELP!
Please, suggest me how I can make the data work on my Droid 4!
Please!
Currently my phone is technically paralyzed because of this issue!
Click to expand...
Click to collapse
Have you checked, that you APN still is entered in the phone ? Upgrade from ICS to JB removed my manual APN entry. I just re-entered it and all working.
/M
I wonder why they axed sleep mode, I used that a lot. Does CM or AOKP still have it?
Sent from my DROID4 using Tapatalk
I've noticed that I'm seeing 3G/H notification in the notification bar while connected on WiFi. It didn't do this in ICS. I wonder whether that's just a cosmetic change or whether it has an impact on battery life. I've not noticed the shift problem, but the Caps Lock light doesn't seem to work any more.
Cheers,
Steve
I can't post this on the Milaq thread (where most of the invisiblek discussion is) so I thought I would post it here to give anyone else a heads up.
The Good:
It's a fairly stable kernel and all my apps run seemingly just fine. I mean I've only been running it about 5 hours but not a single FC. I did have a weird bootup glitch that locked it up right away after install but after that I loaded all the apps just fine. Super exciting to see it so far!
The Bad:
Screen pixelation/tearing from left to right, especailly on grey backgrounds. Something is up with the video driver/gpu voltage. Certain icons like the Settings sprocket will have a few pixels that will flash and other times you'll see lines all the way across the screen. It might be color specific. I was playing Quadropus Rampage and never noticed it but then went back to the home screen or typing an e-mail and it's very much there.
Pandora plays music fine. If you turn off the screen while playing, horrific things happen like ZZZZZZZZZZZZ and then hard lock. I didn't like that station anyway..
The "OK Google" voice command doesn't seem to work though voice typing does. I'm pretty sure this worked on the Milaq build of the same date.
It's a bit slow and CPU is stuck to 1188. There is a bit of a lag switching apps but I don't notice any core functions slow.
The Different:
The home button doesn't wake up the TP. Only the power button.
Can't say anything about battery life quite yet but I'll keep a gander on it. Battery hasn't been a super concern of mine because I plug it in ever night
The Different:
The typical 15 second reset switch mult-button key is more like 3 seconds now. I like this a lot better.
Positive:
--backup and restore work
--it is getting much better.
Negatives:
--Microphone does not work, so I could not use any vioce search or voice dialer/sound recorder.
--Free game "F.S. Xtreme" has black box issue.
--Youtube still has reboot issue.
--TV streams app "syncbak" has similar reboot issue.
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Switched to milaq's 3.0 kernel.
The CPU is pre-configured to run at much higher 1.5Ghz, yet the 3.0 rom is still able to run very stable.
I am waiting for camera fix to enable video calls.
Since both 3.0/3.4 rom are using the same CWM, it makes 3.0/3.4 rom switch very easy.
Waiting on Flintmans as it is the only non data media rom. Not a big fan of all the repartitioning. For several reasons. Good to see choices still available. God bless the developers for all their time and effort. Wish I could do what they do.
goog888 said:
Switched to milaq's 3.0 kernel.
The CPU is pre-configured to run at much higher 1.5Ghz, yet the 3.0 rom is still able to run very stable.
I am waiting for camera fix to enable video calls.
Since both 3.0/3.4 rom are using the same CWM, it makes 3.0/3.4 rom switch very easy.
Click to expand...
Click to collapse
I flashed 3.4 rom (0103) over 3.0, and tried briefly.
--3.4 rom seems running OK, except it runs relatively slower at 1.1Ghz.
--camera is not working on both 3.0/3.4 rom.
--Free game "F.S. Xtreme" seems not compatible with 3.x kernel. It also cannot run on Samsung S3.
Moody66 said:
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Click to expand...
Click to collapse
Turn off WiFi Optimization in settings.
EbolaCola said:
Turn off WiFi Optimization in settings.
Click to expand...
Click to collapse
Still does it. Did that soon as rom booted as per the Op.
Moody66 said:
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Click to expand...
Click to collapse
Same here. Also double check that the setting took. I swear I unchecked it and it went back or didn't take the first time. Perhaps give it a toggle or two. I also noticed that if wifi turns off, it won't turn back on.
Anyone else having a problem with rebooting from within CM and it just goes to a blank screen?
Dirty flashed to the 1/5 nigthly. Reboot issues seems gone now, or just that a reflash has fixed mine specifically.
Just noticed that there is an official thread over at http://forum.xda-developers.com/showthread.php?t=2592909
Hopefully I can post there too!
sokratz said:
Just noticed that there is an official thread over at http://forum.xda-developers.com/showthread.php?t=2592909
Hopefully I can post there too!
Click to expand...
Click to collapse
Negative on the posting. I'm still seeing the bzzzz when the screen shuts off while playing music. Have disabled the mic (I think). Curious that nobody on that thread has reported that quite yet.
I'm very excited to see all of this development on our old TPs! I'm currently running Milaq's latest 3.0 kernel test build. It is running almost perfectly for me! I cannot wait for 3.4 to finish getting smoothed out. I've tried Invisiblek's builds out, and they currently seem a little laggy compared to Milaq's 3.0 test build. Great work all around though! Thanks to Invisiblek, Flintman, Milaq, JCSullins, Dorregary, and all of the others that I haven't mentioned who have contributed so much of their time and skill toward keeping our Touchpads relevant, even competitive with the current crop of tablets on the market!
Sent from my TouchPad using Tapatalk 4
OmniROM
Lollipop - Android 5.x
A new "unified" Galaxy Tab 2 section was added to our forum because we don't make a difference between p31xx an p51xx specific roms.
Please use the Thread here for Omni 5 related questions and feedback
Reserved
Downloads:
Unofficial Builds by me
ROM Downloads for all supported devices can be found here
SuperSU http://download.chainfire.eu/supersu
GApps:
by @Deltadroid http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
or http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
Can't wait to try this out. Loved omnirom ROM 4.4.4 on my tab until I tried your recent SlimLP ROM on it
Sent from my Nexus 5 using Tapatalk
New builds late this evening
Send from OnePlus One using Tapatalk
Android-Andi said:
New builds late this evening
Click to expand...
Click to collapse
Will definitely try this out - Omni 4.4.4 was perfect - I expect nothing less here (over time of course). Thanks Andi.
Builds are up
Send from OnePlus One using Tapatalk
FYI... Cant get it to boot! First tried with dirty flash from SlimLP then a clean... But no luck. Get stuck on bootscreen...
cheeseous said:
FYI... Cant get it to boot! First tried with dirty flash from SlimLP then a clean... But no luck. Get stuck on bootscreen...
Click to expand...
Click to collapse
Likewise with a P5113 here, booted first time after clean flash with pico Gapps and supersu 2.40... but after first reboot and 2 force reboots... still hanging on boot screen with a blank faced android blinking and wondering. Black to SlimLP for now. Thanks again Andi.
Lolli!
I installed the latest build and its working great in my P5110
I didn't even had any major bug yet (Only clock app not working)
Android-Andi said:
Builds are up
Click to expand...
Click to collapse
Reporting: Did an update from last years version.
Wiped C + DC
Flashed Rom + SuperSU
Rebooting .... took approx. 7 minutes ... done
Settings done,
Reboot,
Stuck at boot logo ... left for about 15 minutes
Wiped C + DC again,
Rebooted successfully this time.
Used for an hour or two, than reboot again, stucked at boot logo again...
After wiped C + DC again without no apparent reason: Booting successfully.
Restoring SlimLP with TWRP. Will test next build Andy when available.
@Gregzi thx for testing. I'll run new builds tonight...
Send from OnePlus One using Tapatalk
Testing Build 20150107
Testing latest build:
- Clean flash Rom + Gapps + Supersu 2.40
- Boot time reduced to 3 minutes
- Setting everything
- Noticed that SuperSU is this time correctly pushed into the system (in previous builds I had two:
one in Launcher and one in Settings ==> sometimes problems with root - TBackup)
- Shutting down the tablet
- Booting - again stuck at Omni boot animation (left it for about 10 minutes)
- Force reboot to TWRP (with two button combo)
- Reboot into the system from TWRP without cleaning anything
- Booting normally in 1 minute
When OC the frame rate is now 32,8 fps (Nenamark2), so better than previous builds, so certain progress is done.
The tablet feels smoother - especially noticeable when opening app drawer.
BR
installed over omni 4.4.4 without wipe.
first boot took about 40 mins, updating 173 apps.
some bugs:
firefox beta won't run
home button does not work
still collecting experience, but it doesn' t look too bad ?
Cheers and thanks alot, s.
sent over omni
sebastel23 said:
installed over omni 4.4.4 without wipe.
first boot took about 40 mins, updating 173 apps.
some bugs:
firefox beta won't run
home button does not work
still collecting experience, but it doesn' t look too bad
Cheers and thanks alot, s.
sent over omni
Click to expand...
Click to collapse
Home button gets fixed by flashing Gapps!
DarKnighT916 said:
Home button gets fixed by flashing Gapps!
Click to expand...
Click to collapse
thanks, but actually i had flashed Gapps (pico) already just after the ROM.
however, i'll try again later. :fingers-crossed:
in the meantime, i re-flashed gapps, with no change in behaviour.
for the time being, i'm back to 4.4.4.
bt issues
cannot connect bt headset. other features working fine, any toughts
only a question
I have a p5110 and runs pretty well but I've a problem with the minimum brightness it's very dark I can't see anything. any solution?
I loaded the 1/29 build last night on a clean install (with the latest Nano PA Gapps and SuperSU install zip, all on Andi's latest TWRP build). So far so good, here's a few observations:
-The first boot took a pretty long time but from what I've read this is normal. I didn't reboot again until the next day but for the second boot, the bootanimation never loaded, it just went straight from the brand logo to the launcher, long black wait in between. After that, all fine. Later I loaded the stock lollipop bootanimation I had been using previously (I do like the omni one a lot, though), and it used to lag a bit at the end on 4.4.4 but now it runs smooth all the way through, so that's encouraging.
-Turning the screen off (or letting it time out) is usually buggy, the screen flickers on/off for a second instead of any type of animation (I believe Lollipop is supposed to do a monochrome fadeout?) Edit: On closer inspection I see it is doing the monochrome fade, but then the screen flashes at the end of the animation.
-Re-installing apps was painfully slow and seemed to hang if I let the screen turn off (I'd find it sitting on the same install several minutes later). Downloading seemed a lot slower than KitKat ever was, too. I looked at the stats in settings->apps->running at on point in the process and the Play Store was listed as Restarting, perhaps this indicates poor memory management? Running the app in the foreground didn't seem to help at all, though.
-The material updates to the stock browser app are pretty swanky, I'm a fan. (I saw that in the gerrit and got excited. Not done yet but looks great.)
-Cast screen doesn't seem functional, doesn't find my chromecast. I've tested both Netflix and Localcast to connect just fine, LocalCast was a bit finicky the first time I tried but I think that may have been a network issue.
-I was testing a video call in in Hangouts and tried to mute the sound (was testing with my phone in hand and there was audio feedback loops because of that), but couldn't. Using the volume buttons, it wouldn't go all the way down, and if I dragged the bar the rest of the way it just wouldn't stick. Not sure exactly which volume control that was (lollipop's sound settings still confuse me in general), but I think it must be a bug of some sort that it wouldn't go down to mute.
-I had only just got around to trying to use my tablet's IR blaster (P5113) for TV control a few days earlier, and I found that the top several smart remote apps in the store don't work at all. Peel actually forces a soft reboot when it gets to the "push this button to test turning the device on" step, consistently. I did get one app working, which only includes remote IR support as a secondary function, TV Guide by Mini Group. Unfortunately the app isn't quite polished enough to be useful to me, but it was notable that it just worked where the others all get nothing. I didn't re-test all of the apps on lollipop but the ones I did(both of the ones linked here and a couple of the others that didn't work) behaved the same way.
-Visual performance generally seems a bit laggy but overall performance is fine (i.e. animations may freeze or lag but the tasks they're covering up don't suffer). Maybe all the animations in lolipop are just a bit rough on older hardware? I find them a bit overdone now that I've played around with things a bit more, personally (not that this reflects on the ROM). I don't really like stuff like shadows bouncing around as I scroll menus, though some of them are a nice subtle touch.
Overall I was happy with KitKat, but I think I'll let lollipop grow on me, these quirks are all minor. Idle battery life seems a bit worse but it's hard to make that call, I've been fiddling with the tablet more than usual to test things anyway.
Edit: Actually after letting it sit overnight unplugged, the idle battery is better than I was ever getting on KitKat. Granted, I made a point of closing all apps before and I think on KitKat I was having issue with casting apps holding wakelocks overnight and that's yet to be tested, but 1% over 12 hours is a pretty damn good baseline. Not sure what caused that wifi drop towards the end, after holding the connection (it gets a good strong signal) for about 11 hours, though.
Hey together!
Seems like we have some faulty eMMC chips, some reports of broken devices appeared.
I pushed a commit to address the issue and prevent other devices from damage.
I will recompile latest Lollipop roms and recoveries within 1 week.
For more information please read http://forum.xda-developers.com/showthread.php?t=3016879
Follow the instructions please to check your eMMC information.
Best regards and wishes!
Andi
Send from OnePlus One using Tapatalk
Internet sharing (mobile hotspot) doesn't work