Hi everyone
Alpha 2.1 is Released!!!
http://rootzwiki.com/showthread.php?4011-RELEASE-ALPHA-Discussion-CyanogenMod-team-Touchpad-port
Post feedbacks, bugs and thoughts!
Installed alongside 3.0.3; no issues. The instructions were well-written, so I didn't have any trouble.
Seems to work well enough, haven't had a chance to extensively play with it.
... don't se the other several page long thread..
Posted from my cm7 alpha already! Now to install a thumb/split keyboard.. oh how I've been waiting for thee
bluetooth works for me. able to transfer files from my Galaxy S2
wifi works too. no drop or such.
gapps installed and could access certain market apps
most games i played on my Galaxy S2 works on the TouchPad
mass storage device works with 10gb of useable space
double boot was right on! though it takes alittle longer to start webos.
got me thinking if it was stuck at the HP logo
all in all great work. Your call this an alpha release?
Kudos to the CyanogenMOD team!
Those calls in the video were hilarious, I like the way they "called just by chance"
Works quite well, seems to die quite a bit when I lock it and then it won't wake up or it will wake up and the touchscreen won't work. I'm impressed though. Thanks CM Team.
help!!!
can anyone help me. im trying to do the command for acme installer but its not going thru in novcam. im trying to install from my pc windows 7. any suggestions?
No Clockwork Recovery
Somehow when I installed cm7 the clockwork recovery did not make it on to the touchpad. Any ideas about how I can write the recovery image now that it has this multi boot functionality? Without
recovery I can't push google apps....Any help would be appreciated.
---------- Post added at 03:13 PM ---------- Previous post was at 02:24 PM ----------
Somehow when I installed cm7 the clockwork recovery did not make it onlt the touchpad. Any ideas about how I can write the recovery image now that it has this multi boot functionality? With recovery I can't push google apps....Any help would be appreciated.
cbogiages said:
Somehow when I installed cm7 the clockwork recovery did not make it on to the touchpad. Any ideas about how I can write the recovery image now that it has this multi boot functionality? Without
recovery I can't push google apps....Any help would be appreciated.
---------- Post added at 03:13 PM ---------- Previous post was at 02:24 PM ----------
Somehow when I installed cm7 the clockwork recovery did not make it onlt the touchpad. Any ideas about how I can write the recovery image now that it has this multi boot functionality? With recovery I can't push google apps....Any help would be appreciated.
Click to expand...
Click to collapse
I know ROM Manager is included so maybe you can flash it through that if it has the touchpad version.
Sent from my Nexus S running NSCollab ROM and Trinity T144 Beast Kernel.
Rom manager is only partially functional right now. As long as you reboot to recovery it works fine, though the CWM GUI still needs some work. Remember,we are using alpha software here. That said, other thanthe occasional app, the only issue I have really seen so far is some codex problems, occasional wifi drops and assorted odds and ends. CM did amazing work! I've tested beta software with more issues.
Sent from my HP Touchdroid using xda premium
Ok... First Thanks CM for getting this to us! Its very nice to have touchpad running Android.
I decided to try a couple things and now i can't revert back to find out and hoping some in here can help me.
I tried porting honeycomb over to the touchpad. Well it installed just fine, but now it seems as tho I have a hybrid of a rom. I have 2g/3g stuff (nothing works on there) but have adwlauncher and many more settings.
So, my question is, can someone pm me that is running this to see if we can compare systems. I can't format and go back to test things cause i tried.
Thanks,
~leo
Alpha 2.1 released!!!
updating now
xenocide976 said:
Alpha 2.1 released!!!
updating now
Click to expand...
Click to collapse
How do you update it?
Sent from my Nexus S running NSCollab ROM and Morfics Thermite Beast Kernel.
Why is this in WebOS Software Development category?
Just installed 2.1 on my Touchpad and it is pretty impressive for only being in Alpha stage.
benrees21 said:
How do you update it?
Sent from my Nexus S running NSCollab ROM and Morfics Thermite Beast Kernel.
Click to expand...
Click to collapse
copy the new update.....zip to the "cminstall" folder
then run novacom command and it will install the new 2.1 alpha
if u recently updated to webos3.0.4, u will need to start all over again for CM7 as it has deleted the moboot from /boot
xenocide976 said:
copy the new update.....zip to the "cminstall" folder
then run novacom command and it will install the new 2.1 alpha
if u recently updated to webos3.0.4, u will need to start all over again for CM7 as it has deleted the moboot from /boot
Click to expand...
Click to collapse
Thanks.
Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
been working good for me for the past couple days
yah... been working good for me thus far too!
Only bit I'm confused about is what terminal to run novacom ? Bash, dos prompt ?
Sent from my GT-I9100 using XDA App
Related
At the suggestion of others, I put this in its own thread.
First of all, credit goes to Watsa for his work on Pinnacle. The ROM I posted yesterday was built with the Android kitchen and somehow was breaking WiFi (and root). So I used the Android kitchen to just deodex /app and /framework this time around and merged that into Pinnacle 1.3. This is not Pinnacle based by any means (ot Pinnacle tweaks or UI, etc.), I just used it to embed the ROM with rooting capabilties and edited the update script slightly.
Everything is stock here besides removing AT&T bloat, deodexing, zip-aligning, and root. The kernel and modem are stock I897UCKI2. There are NO BOOTLOADERS within this ZIP. So you must be running a Gingerbread ROM already.
I am running it right now with WiFi and root working. I was able to use TiBu to restore 90+ apps as well.
http://www.mediafire.com/?7dl8b8wxmn043b9
Let me know how it goes.
emuneee said:
At the suggestion of others, I put this in its own thread.
First of all, credit goes to Watsa for his work on Pinnacle. The ROM I posted yesterday was built with the Android kitchen and somehow was breaking WiFi (and root). So I used the Android kitchen to just deodex /app and /framework this time around and merged that into Pinnacle 1.3. This is not Pinnacle based by any means (ot Pinnacle tweaks or UI, etc.), I just used it to embed the ROM with rooting capabilties and edited the update script slightly.
Everything is stock here besides removing AT&T bloat, deodexing, zip-aligning, and root. The kernel and modem are stock I897UCKI2. There are NO BOOTLOADERS within this ZIP. So you must be running a Gingerbread ROM already.
I am running it right now with WiFi and root working. I was able to use TiBu to restore 90+ apps as well.
http://www.mediafire.com/file/7dl8b8...xed_rooted.zip
Let me know how it goes.
Click to expand...
Click to collapse
link says file invalid or missing
Did you pull the file?
Sorry, link got mangled when I copied and pasted. Fixed in OP.
http://www.mediafire.com/?7dl8b8wxmn043b9
emuneee said:
Sorry, link got mangled when I copied and pasted. Fixed in OP.
http://www.mediafire.com/?7dl8b8wxmn043b9
Click to expand...
Click to collapse
downing ......
I think you should add deodexed/zipaligned/rooted in the OP...
EDIT:
Works smoothly...flashed over fasty II V2.0 but am gonna back to Fasty mostly just keeping this for a day I think..not a stock kinda guy
Nice work emuneee.
And on a side... checked out ur website---very good stuff there as well.
is this the exact same CWM version that was in the body of the other I897UCKI2 thread?
Nice work. Thanks for putting this together. Unfortunately, my office firewall blocks the server you uploaded it to. If anyone can put in on a dropbox I would really appreciate it.
*DISREGARD*
I killed TIBU from task manager...restarted it and it restored fine
------------------------------
---------- Post added at 10:53 AM ---------- Previous post was at 10:52 AM ----------
[/COLOR]has anyone successfully restored apps from TIBU after installing this?
I did flash boogs kernel after the flash as well.
Tried restoring from TIBU and stuck on the first APP at 0% with no progression?
---------- Post added at 10:59 AM ---------- Previous post was at 10:53 AM ----------
Nice work! I was running into the same issue you were yesterday with wifi being broke. Curious to know what you did to fix it.
NVM! Didn't read the entire OP.
terher manager apk
Did you already pull the Tethering Manager APK from the system/apps folder or are they using a differently named apk now? It was in my system app folder?
bames said:
Did you already pull the Tethering Manager APK from the system/apps folder or are they using a differently named apk now? It was in my system app folder?
---------- Post added at 10:53 AM ---------- Previous post was at 10:52 AM ----------
has anyone successfully restored apps from TIBU after installing this?
I did flash boogs kernel after the flash as well.
Tried restoring from TIBU and stuck on the first APP at 0% with no progression?
Click to expand...
Click to collapse
In setup, make sure that you enable debug mode, unknown apps. Works great for me. I injected boogs 1 kernel, then booted and flashed the K1 K2 boogs kernel with init.d. I also injected the attached battery mod for a circle battery, just cant handle the stock battery. I can't seem to get that Powermenu that has been posted to work though.
golfslicer said:
In setup, make sure that you enable debug mode, unknown apps. Works great for me. I injected boogs 1 kernel, then booted and flashed the K1 K2 boogs kernel with init.d. I also injected the attached battery mod for a circle battery, just cant handle the stock battery. I can't seem to get that Powermenu that has been posted to work though.
Click to expand...
Click to collapse
ya i flashed the power menu also through cwm and it didn't take for me either
golfslicer said:
In setup, make sure that you enable debug mode, unknown apps. Works great for me. I injected boogs 1 kernel, then booted and flashed the K1 K2 boogs kernel with init.d. I also injected the attached battery mod for a circle battery, just cant handle the stock battery. I can't seem to get that Powermenu that has been posted to work though.
Click to expand...
Click to collapse
Powermenu not wanting to work for me either. Odin Boog 1 and then flashed Boog 2 with CWM. The ROM is working nice.
golfslicer said:
In setup, make sure that you enable debug mode, unknown apps. Works great for me. I injected boogs 1 kernel, then booted and flashed the K1 K2 boogs kernel with init.d. I also injected the attached battery mod for a circle battery, just cant handle the stock battery. I can't seem to get that Powermenu that has been posted to work though.
Click to expand...
Click to collapse
Awesome! +10char
[ edit/update ]
I get it. It's flash-able via CWM (which isn't possible on STOCK 2.3.x -->d'oh.)
I flashed Pinnacle ROM on my i897 (which has CWM v4x included -- sweet), saw how awesome it is; and flashed it to my wife's (Mrs. metalchef) i897 immediately (funny how there's no CWM or rooting method for 2.3.x, yet all the ROMs based off of this release come pre-rooted & incl CWM...I don't get it)
She has since commented on how fast this ROM is (vs say... FastyIIv2, which is what I had flashed to her device previously).
sorry for the silly post. derrrr
I can haz CWM.
Glad it seems to be working for everybody!
metalchef said:
Since this is in .zip format, how am I to apply/flash this to my device? (All I'm looking for here is su/root capabilities with 2.3.x)...is this not meant to be used by non-devs?
Click to expand...
Click to collapse
If your phone is already running a Gingerbread Rom, just flash it using CWM recovery.
emuneee said:
If your phone is already running a Gingerbread Rom, just flash it using CWM recovery.
Click to expand...
Click to collapse
and make sure that you disable lagfix first, that is if you are running it.
It's been requested that I create a new thread for this so as not to clog up @milaq's thread.
As some of you may have seen in flintman's Evervolv and milaq's CM threads, there has been a lot of work on the 3.4 kernel for tenderloin. Its a pretty awesome feat to have this running on our good ol tenderloin. =)
The gratitude for this kernel and build needs to be given to almost anyone but me. (Flemmard, flintman, jcsullins, Dorregaray and everyone that came before me on this device (dalingrin, green, and other's I'm sure that I'm missing)). I've had my tenderloin for quite awhile but never really done much with it until recently.
Anyway, without further ado, I present to you nightlies of CM-11.0 for tenderloin with a 3.4 kernel and -caf based HALs. Basically what this means is we'll be running the latest code from codeaurora on our msm8660 tenderloin.
THERE WILL BE BUGS! This thing is not perfect. It is still in active development.
CURRENT BUGZ (in no particular order):
- Bluetooth steals battery, but DOES work (jcsullins) - also sixaxis app doesn't work =(
- Camera is a bit derpy still, major wip, it takes pictures though (Dorregaray)
- Other stuff? Probably, yea
Destructions: PLEASE READ
1. This is a /data/media rom (relevant). What that means is you should be partitioned with a very small 'media' partition and a very large 'data' partition. The benefit of this is that your /sdcard and /data partitions share the big chunk of your usable space, just like any newer phone does these days. Use TPToolbox to achieve the new partition scheme: http://forum.xda-developers.com/showthread.php?t=2756314
2. You'll need a recovery that has both /data/media support and selinux support. Any of the following will work. Flashable via recovery.
-PhilZ Clockworkmod 6.0.4.7 (non-touch)(will backup and restore in both cwm and twrp format)
-Milaq's ClockworkMod 6.0.5.4
-Flintman's TWRP
3. Now you're ready to flash the rom. Downloads here: http://www.invisiblek.org/roms/cm-11.0/tenderloin/
4. Gapps here: http://wiki.cyanogenmod.org/w/Google_Apps
I'd recommend wiping data when coming to this rom or going to a different one (going between milaq's and this should be fine).
These are automatically built on my personal server at home and then uploaded. There may or may not be issues during the build times so don't always expect a fresh build every day. You can follow the automated twitter account here which will spit out a tweet once the build is finished uploading.
Sources:
-Kernel
-Device Tree
-CM Sources (the rest of what's needed)
There are a couple more changes and a couple other repos that are required to build this. Add this stuff to your .repo/local_manifests/roomservice.xml in order to build this yourself (after syncing the cm source of course)
http://pastebin.com/jKAMWM8T
You'll also need to cherry pick this commit from jcsullins: http://review.cyanogenmod.org/#/c/54380
Feel free to fork and fix!
Again -
Thanks to everyone that has contributed to making this rom.
Flemmard, flintman, jcsullins, dalingrin, green, milaq, the entire CM team and I'm sure many others.
Good new year present.
Looking forward to when Bluetooth is working. That and the black boxes were the only thing keeping me off KitKat.
Sent from my TouchPad using XDA Premium 4 mobile app
invisiblek, I used your 20131226 ROM. It kept crashing and rebooting every time I played a video. Netflix would crash immediately on loading and reboot the tablet. Has this been fixed with your 20131231 build?
Sent from my Touchpad using Tapatalk
---------- Post added at 08:53 PM ---------- Previous post was at 08:39 PM ----------
I almost forgot… I also had major issues with apps not installing or disappearing after a reboot.
Sent from my Touchpad using Tapatalk
i am trying to move uImage.ClockworkMod after rename the file its asking file already exit ,should we need to replace ?
i tried to keep both but it never successful...
is there any way to intall from zip file like upgrading recovery
k4ever said:
invisiblek, I used your 20131226 ROM. It kept crashing and rebooting every time I played a video. Netflix would crash immediately on loading and reboot the tablet. Has this been fixed with your 20131231 build?
Sent from my Touchpad using Tapatalk
---------- Post added at 08:53 PM ---------- Previous post was at 08:39 PM ----------
I almost forgot… I also had major issues with apps not installing or disappearing after a reboot.
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
I believe Flint said video playback was still a bit broke around that date. I remember loading that build and Diceplayer would crash upon playing a video, but it would only crash back to the home screen (not entirely crash and reboot). I think Flint said he fixed it earlier, so try 20140101 when it comes out.
vinukondamahesh said:
i am trying to move uImage.ClockworkMod after rename the file its asking file already exit ,should we need to replace ?
i tried to keep both but it never successful...
is there any way to intall from zip file like upgrading recovery
Click to expand...
Click to collapse
Replace it so you can use the new CWM to flash this build. I believe /boot is limited to 30mb so trying to keep both may not work.
allstar319, what about the disappearing apps? Has that been fixed?
Sent from my Touchpad using Tapatalk
k4ever said:
allstar319, what about the disappearing apps? Has that been fixed?
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
No clue. I heard of apps disappearing from the Google Home Launcher, but not getting completely removed or preventing apps from being installed. Is that the launcher you're using? Only remedy I heard from that (Milaq's CM11 thread, somewhere around page 40) was to just readd them from the app drawer.
Best advice is to wait for todays build to get uploaded and see what happens.
2. You'll need a recovery that has both /data/media support and selinux support. This clockworkmod will do the trick: http://invisiblek.org/tenderloin/openrecovery-twrp-2.6.3.0-tenderloin-selinux.img (thanks @milaq)
Push it to /boot/uImage.ClockworkMod
Great ROM far, I loaded the recovery but i named it TWRP instead because it says TWRP in the file name. It ran as TWRP . Is the above just a typo or can I call it either one?
Sent from my Touchpad using XDA Premium HD
allstar319 said:
I believe Flint said video playback was still a bit broke around that date. I remember loading that build and Diceplayer would crash upon playing a video, but it would only crash back to the home screen (not entirely crash and reboot). I think Flint said he fixed it earlier, so try 20140101 when it comes out.
Replace it so you can use the new CWM to flash this build. I believe /boot is limited to 30mb so trying to keep both may not work.
Click to expand...
Click to collapse
thank you its working nw
milaq actually has a flashable zip in his thread. that is the easiest. i was on 4.3 went into that recovery, made a backup then flashed the new cwm, rebooted recovery did a full wipe and flashed the rom and gapps and i am up and running. who would have ever thought we would have kitkat on a touchpad. not to mention a 3.x kernel. unreal, thanks for everyones work. Happy New Year
jerryatherton said:
2. You'll need a recovery that has both /data/media support and selinux support. This clockworkmod will do the trick: http://invisiblek.org/tenderloin/openrecovery-twrp-2.6.3.0-tenderloin-selinux.img (thanks @milaq)
Push it to /boot/uImage.ClockworkMod
Great ROM far, I loaded the recovery but i named it TWRP instead because it says TWRP in the file name. It ran as TWRP . Is the above just a typo or can I call it either one?
Sent from my Touchpad using XDA Premium HD
Click to expand...
Click to collapse
Oops, I had the wrong image there. Link updated with the cwm =P
EDIT: Also added a flashable zip for it, had trouble downloading milaq's so I made my own =/
Anyone else getting a Core Process failure message when booting to the 01012014 Build?
I went back to the 12312013 build and all appears to be back to normal.
To be clear, I went straight to this build from a fresh CM9 image without booting into Android - ever. Got a second-hand device back from a relative, and pushed it to CM11, so it may have been a result of my own process.
I'll reflash 01012014 and see if the error persists.
--McBean
Really looking forwards to a stable version of this to try. Thanks for the effort.
BillzillaAus said:
Really looking forwards to a stable version of this to try. Thanks for the effort.
Click to expand...
Click to collapse
So am I. Right now I'm using invisiblek's CM 10.2 ROM. It's stable (although a little slow). I don't want to jump to CM 11 again until it is a lot more stable.
BTW, can someone point me to a thread that discusses that benefits of the 3.4 kernel on the Touchpad?
Sent from my Touchpad using Tapatalk
k4ever said:
So am I. Right now I'm using invisiblek's CM 10.2 ROM. It's stable (although a little slow). I don't want to jump to CM 11 again until it is a lot more stable.
BTW, can someone point me to a thread that discusses that benefits of the 3.4 kernel on the Touchpad?
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
IIRC, a long time ago, someone mentioned that there were some benefits of Jelly Bean that we couldn't use because of the version of our kernel we were using. I would assume the same still applies today if that was the case. Also, with CM11, black boxes are present in many apps that prove them to be unusable. The default browser is unusable on CM11 with the old kernel, so you'd have to either use Chrome, or wait for a new kernel. I'm sure there are some performance enhancements as well.
On todays build, video playback still seems to crash to the home screen with Diceplayer (I could of swore Flint said he fixed that in his build at least). I haven't tested Milaq's test build of the 3.0 kernel to see if that's the same case over there.
allstar319 said:
IIRC, a long time ago, someone mentioned that there were some benefits of Jelly Bean that we couldn't use because of the version of our kernel we were using. I would assume the same still applies today if that was the case. Also, with CM11, black boxes are present in many apps that prove them to be unusable. The default browser is unusable on CM11 with the old kernel, so you'd have to either use Chrome, or wait for a new kernel. I'm sure there are some performance enhancements as well.
On todays build, video playback still seems to crash to the home screen with Diceplayer (I could of swore Flint said he fixed that in his build at least). I haven't tested Milaq's test build of the 3.0 kernel to see if that's the same case over there.
Click to expand...
Click to collapse
Thanks for the quick reply. Bummer!
Sent from my Touchpad using Tapatalk
---------- Post added at 04:59 PM ---------- Previous post was at 04:48 PM ----------
One more question for invisiblek, will you be making any updates/improvements to CM10.2 or has all development shifted to CM11? The last 10.2 ROM was on 20131209. I'm having issues with the camera not working..
Sent from my Touchpad using Tapatalk
k4ever said:
Thanks for the quick reply. Bummer!
Sent from my Touchpad using Tapatalk
---------- Post added at 04:59 PM ---------- Previous post was at 04:48 PM ----------
One more question for invisiblek, will you be making any updates/improvements to CM10.2 or has all development shifted to CM11? The last 10.2 ROM was on 20131209. I'm having issues with the camera not working..
Click to expand...
Click to collapse
Also, the old kernel was preventing us from having "official" CM builds.
Getting SoD's once I turn the screen off. Tried the old way to fix that by raising the min clock, but that didn't seem to help. Any ideas?
k4ever said:
Thanks for the quick reply. Bummer!
Sent from my Touchpad using Tapatalk
---------- Post added at 04:59 PM ---------- Previous post was at 04:48 PM ----------
One more question for invisiblek, will you be making any updates/improvements to CM10.2 or has all development shifted to CM11? The last 10.2 ROM was on 20131209. I'm having issues with the camera not working..
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
The 3.4 kernel, minimally, resolves an issues with the other CM11 builds where the core/stock apps were experiencing "black boxes" which prevented users from reading mail, using the browser to navigate and some other issues. Right off the bat, the new kernel resolves that issue.
--McBean
For those that don't know what evervolv is, Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
Right now the current source we are working on is KITKAT(Android 4.4.4).
Current version: 4.0.0p1
Current Items not working/Buggy
Updated 4-4-14
Bluetooth working --Still a WIP as some devices don't connect
Camera working --Still a WIP as the camcorder records in blue and a few minor issues
home key doesn't turn device on need to use power button--FIXED in the next nightly should be 4-5-2014
Battery draw around 50mA in sleep
Some experience SOD when hotword detect is active
Location service has stopped with Googles update looking into now
You tell me what you find.
4G Models are not currently supported
Click to expand...
Click to collapse
Evervolv Github: https://github.com/Evervolv
Evervolv Gerrit: http://review.evervolv.com/
Evervolv website: http://www.evervolv.com/
(New Site is up Check it out)
Evervolv Bug Tracker: http://bugs.evervolv.com/
(Please have discretion when reporting issues, and be descriptive / helpful. Also understand that we'll have some growing pains with this. So don't expect everything to be perfect.)
Twitter: https://www.twitter.com/wbellavance
IRC: #evervolv
Click to expand...
Click to collapse
[GPL Compliance]
Kernel Source
Click to expand...
Click to collapse
[Download]
If you already have evervolv installed you should see this build under testing if you refresh and can download that way.
No more nightlies Moved to 5.0 Lollipop
ev_tenderloin-1-23-15 Last and final for 4.0 -> Fix netflix
FLINTMAN-TWRP-touch-data_media-SELINUX-2.7.1.0-6-7-2014.zip
--This is a flashing TWRP recovery with data/media and SELINUX support. I have tested 100% of the features and everything is working great as far as i can tell. Soo
with that being said. Use at your own risk 8). Make sure you save a backup from your current recovery just in case. BACKUP BACKUP BACKUP
--Broke Vibration as i updated kernel.
Click to expand...
Click to collapse
NOTE: Recommend a clean install if moving from a previous version and or another ROM.
Flashing from cm or any other ROM will require a clean install, dirty flashes can cause random reboots and random errors
[Disclaimer]
I am not responsible for bricked devices, lost data, etc, etc. You all know the drill. BACKUP BACKUP BACKUP
Click to expand...
Click to collapse
[Special Thanks]
i would like to thank Flemmard, Jcsullins, Dorregaray, Invisiblek, Milaq, and anyone else that helped to make this happen. More great work to come.
Mitchbaria --for a 4g model to start in on this
Colchiro-- For a spare Touchpad WIFI to be able to test on one and develop at the same time
Click to expand...
Click to collapse
GAPPS
---These are the gapps i use. You should be able to use any that are KitKat compatible
http://forum.xda-developers.com/showthread.php?t=2397942
Grabbing logcats and dmesg along with last_klog.
These are helpful in figuring out what is going on
Install the sdk in you PC http://developer.android.com/sdk/index.html
Logcat
"adb shell logcat >logcat.txt"
This will run until unplugged or ctrl c and all the content will go into that file
dmesg
"adb shell cat proc/kmsg >dmesg.txt"
This will run until unplugged or ctrl c and all the content will go into that file
Last_klog
"adb shell cat proc/last_klog >lastklog.txt"
This is for if you have a reboot run this right after the device starts back up and it will get me the last dmesg from before it reboot and will help determine the cause of the reboot.
This will help me and everyone that uses this ROM as i can determine the cause of issues.
Thanks
Thank you for the continued HP Touchpad Development and support Flintman.
Cheers:highfive:
Touchpad Toolbox By Jcsullins
[ROM GUIDE]How to use the TouchPad Toolbox to install Android "The Super Easy Way"
[GAPPS][4.4.x/4.3.x] OFFICIAL 0-Day PA-GOOGLE APPS (Use Mini or Micro packages)
Thanks to both of you. For the roms and the video walk thru. I haven't tried art on the touchpad because it actually makes my Galaxy Nexus slower most of the time. And with some gapps it's even worse. Since it isn't listed as broken I am assuming you have tried it. If I may ask. What gapps did you use and what was performance like? It prevented my nexus from booting at times. Just wanna stick with what you have tried until I get use to the new data media and such. Thanks again.
Moody66 said:
Thanks to both of you. For the roms and the video walk thru. I haven't tried art on the touchpad because it actually makes my Galaxy Nexus slower most of the time. And with some gapps it's even worse. Since it isn't listed as broken I am assuming you have tried it. If I may ask. What gapps did you use and what was performance like? It prevented my nexus from booting at times. Just wanna stick with what you have tried until I get use to the new data media and such. Thanks again.
Click to expand...
Click to collapse
I haven't tested as its still a wip from Google. I do have it as broken in the op. But good to know that it boots 8)
Sent from my SCH-I545 using xda app-developers app
Added another build see OP for what was changed. I also adding in a touch recovery TWRP with data/media and SELINUX support. This will also allow you access to your webOS media folder which is know in the new build as external_sd. I have tested out all the features and everything is working great but please save a full backup from your previous recovery if you decide to use this recovery as it's still in an Alpha state.
Enjoy
flintman said:
Added another build see OP for what was changed. I also adding in a touch recovery TWRP with data/media and SELINUX support. This will also allow you access to your webOS media folder which is know in the new build as external_sd. I have tested out all the features and everything is working great but please save a full backup from your previous recovery if you decide to use this recovery as it's still in an Alpha state.
Enjoy
Click to expand...
Click to collapse
Thanks a lot for this amazing ROM and the recovery I had few bug with the reboot ... The recovery freezed and i have to manually reboot to unfreeze it ... A part from that great job Can't wait to see what you are going to bring next
And just one little request ... I love having the clock center on the status bar ... Do you think you can add it to the Evervolv project ? That's would be a great feature
Lyok0ne said:
Thanks a lot for this amazing ROM and the recovery I had few bug with the reboot ... The recovery freezed and i have to manually reboot to unfreeze it ... A part from that great job Can't wait to see what you are going to bring next
And just one little request ... I love having the clock center on the status bar ... Do you think you can add it to the Evervolv project ? That's would be a great feature
Click to expand...
Click to collapse
I have flashed with this recovery about 20 times now and only got the reboot to hang once. I'm looking into it.
Lyok0ne said:
Thanks a lot for this amazing ROM and the recovery I had few bug with the reboot ... The recovery freezed and i have to manually reboot to unfreeze it ... A part from that great job Can't wait to see what you are going to bring next
And just one little request ... I love having the clock center on the status bar ... Do you think you can add it to the Evervolv project ? That's would be a great feature
Click to expand...
Click to collapse
install xposed + gravitybox. it works like a charm and has this feature and many others.
Sent from my Nexus 4 using Tapatalk
Okay, I am doing something wrong. I have downloaded the recovery multiple times from multiple devices. I have tried installing via TWRP and manually extracting the image to /boot.
Each attempt, I get:
Checking uImage... Invalid Size
BOOT FAILED!
Please SELECT to continue
Any thoughts? I can still load my backup copy of TWRP without issue.
Update:
After purging the other copies of TWRP from /boot, the new version loads without issue. Thanks flintman!
Discovered that the TP 4G not compatible with the test 3.X Kernel yet
Hey Flintman just wanted to point out my findings after going crazy over the past couple weeks trying to figure what I was doing wrong when flashing the test Kit Kat ROMs w/3.X kernel.
Previously my TP 4G was working fine on shumash's SCHIZOID 4.2.2 ROM but I was extremely eager to try out the new 3.X kernels. I first tried out your non-data/media Evervolv 4.0.0p1 version and was unable to connect to WiFi despite repeated clean install methods and variations of cache wipes. I know that I had re-sized partitions with Tailor sufficiently for Kit Kat as warned so I then attempted to try out Invisblek's CM11 ROM. Not only was WiFi still not wanting to toggle on, but the rotation sensor was acting oppositely for landscape orientations and I was getting frequent crashing reboots just going through the UI. I then decided to try out JCSullins' updated CM10.1 ROM with his 3.0 kernel and then encountered the same behavior as Invisblek's CM11 ROM, but with even worse random touch driver issues that resulted in erratic automatic screen touches and ultimately soft-reboots.
Restoring a backup to SCHIZOID's 4.2.2 ROM worked fine to restore all functionality, but I couldn't help but think that I was still doing something wrong.
I got a hold of a normal TP (WiFi only model) and tried your latest 1-10-2014 Evervolv 4.0.0p1 ROM and was amazed to see that it was working great including WiFi (although 5GHz APs don't seem to scan as reliably as the past kernel) aside from the known issues. I tried the exact same install process on my TP 4G again just to see if anything changed, but unfortunately WiFi still wouldn't toggle and the orientation sensor behavior exhibited the same opposite landscape behavior as Invisiblek and JCSullins' ROMs.
I had thought that aside from the 3G HSPA modem in the TP 4G model chipset-wise it would be identical to the WiFi-only model so kernel 3.X developments would be complimentary across all TP devices. Unfortunately this doesn't appear to be the case and I hope with time you guys are able to work out any compatibility with the 4G model to benefit from the already terrific development that's going on with the 3.X kernel now.
I admire your guys' skills and look forward to all the improvements in store!
PS: I'd be more than happy to beta test anything you guys feel would address any compatibility issues on the TP 4G!
If we flash your twrp will it remove cwm or add another entry? I've never been able to have two recoveries working. I would much rather not have to use the power button and what not all the time in cwm but want to make sure I'm covered if something goes wrong. Thanks
Sent from my TouchPad using Tapatalk
Due to the limit of the boot directory it will remove all recoveries before installing this one.
Sent from my SCH-I545 using xda app-developers app
Sorry for the Nube question I've searched and I'm sure it's been answered already....
So I got my touchpad with ClockworkMod Recovery version 6.0.1.9 can I flash the TWRP SE data/media recovery from there? Trying with the acme installer 5ET has failed.
I do have the original 4.4 Evervolv up and running and my partitions have been updated.
Thanks
Steve
SteveoSupremo said:
Sorry for the Nube question I've searched and I'm sure it's been answered already....
So I got my touchpad with ClockworkMod Recovery version 6.0.1.9 can I flash the TWRP SE data/media recovery from there? Trying with the acme installer 5ET has failed.
I do have the original 4.4 Evervolv up and running and my partitions have been updated.
Thanks
Steve
Click to expand...
Click to collapse
So I replaced the ulimage in the boot directory and was able to install the 1/10/14 rom. So I guess I needed to search and just try a little more.
anyway -- I think it's a little slower than the first 4.4 version.... Maybe I need to reboot.... thoughts?
steve
Both using same cpu settings? Although with more things implemented it could seem slower.
---------- Post added at 01:11 AM ---------- Previous post was at 01:07 AM ----------
emph4tic said:
Hey Flintman just wanted to point out my findings after going crazy over the past couple weeks trying to figure what I was doing wrong when flashing the test Kit Kat ROMs w/3.X kernel.
Previously my TP 4G was working fine on shumash's SCHIZOID 4.2.2 ROM but I was extremely eager to try out the new 3.X kernels. I first tried out your non-data/media Evervolv 4.0.0p1 version and was unable to connect to WiFi despite repeated clean install methods and variations of cache wipes. I know that I had re-sized partitions with Tailor sufficiently for Kit Kat as warned so I then attempted to try out Invisblek's CM11 ROM. Not only was WiFi still not wanting to toggle on, but the rotation sensor was acting oppositely for landscape orientations and I was getting frequent crashing reboots just going through the UI. I then decided to try out JCSullins' updated CM10.1 ROM with his 3.0 kernel and then encountered the same behavior as Invisblek's CM11 ROM, but with even worse random touch driver issues that resulted in erratic automatic screen touches and ultimately soft-reboots.
Restoring a backup to SCHIZOID's 4.2.2 ROM worked fine to restore all functionality, but I couldn't help but think that I was still doing something wrong.
I got a hold of a normal TP (WiFi only model) and tried your latest 1-10-2014 Evervolv 4.0.0p1 ROM and was amazed to see that it was working great including WiFi (although 5GHz APs don't seem to scan as reliably as the past kernel) aside from the known issues. I tried the exact same install process on my TP 4G again just to see if anything changed, but unfortunately WiFi still wouldn't toggle and the orientation sensor behavior exhibited the same opposite landscape behavior as Invisiblek and JCSullins' ROMs.
I had thought that aside from the 3G HSPA modem in the TP 4G model chipset-wise it would be identical to the WiFi-only model so kernel 3.X developments would be complimentary across all TP devices. Unfortunately this doesn't appear to be the case and I hope with time you guys are able to work out any compatibility with the 4G model to benefit from the already terrific development that's going on with the 3.X kernel now.
I admire your guys' skills and look forward to all the improvements in store!
PS: I'd be more than happy to beta test anything you guys feel would address any compatibility issues on the TP 4G!
Click to expand...
Click to collapse
I am curious. Have you tried turning the 4g off. Like airplane mode then just turning wifi back on? Was thinking of getting one of these models to tinker with.
Moody66 said:
Both using same cpu settings? Although with more things implemented it could seem slower.
---------- Post added at 01:11 AM ---------- Previous post was at 01:07 AM ----------
Click to expand...
Click to collapse
I think it was because of sync.... it's running smooth now. after I loaded a different set of GAPPS.
Now I have to figure out the camera apk. it would help if I RTFM.... Thanks Flintman for the awesome update!
Which version of gapps is recommended for 01-10-14 version?
New Test build up which fixes vibration
emph4tic said:
Hey Flintman just wanted to point out my findings after going crazy over the past couple weeks trying to figure what I was doing wrong when flashing the test Kit Kat ROMs w/3.X kernel.
Previously my TP 4G was working fine on shumash's SCHIZOID 4.2.2 ROM but I was extremely eager to try out the new 3.X kernels. I first tried out your non-data/media Evervolv 4.0.0p1 version and was unable to connect to WiFi despite repeated clean install methods and variations of cache wipes. I know that I had re-sized partitions with Tailor sufficiently for Kit Kat as warned so I then attempted to try out Invisblek's CM11 ROM. Not only was WiFi still not wanting to toggle on, but the rotation sensor was acting oppositely for landscape orientations and I was getting frequent crashing reboots just going through the UI. I then decided to try out JCSullins' updated CM10.1 ROM with his 3.0 kernel and then encountered the same behavior as Invisblek's CM11 ROM, but with even worse random touch driver issues that resulted in erratic automatic screen touches and ultimately soft-reboots.
Restoring a backup to SCHIZOID's 4.2.2 ROM worked fine to restore all functionality, but I couldn't help but think that I was still doing something wrong.
I got a hold of a normal TP (WiFi only model) and tried your latest 1-10-2014 Evervolv 4.0.0p1 ROM and was amazed to see that it was working great including WiFi (although 5GHz APs don't seem to scan as reliably as the past kernel) aside from the known issues. I tried the exact same install process on my TP 4G again just to see if anything changed, but unfortunately WiFi still wouldn't toggle and the orientation sensor behavior exhibited the same opposite landscape behavior as Invisiblek and JCSullins' ROMs.
I had thought that aside from the 3G HSPA modem in the TP 4G model chipset-wise it would be identical to the WiFi-only model so kernel 3.X developments would be complimentary across all TP devices. Unfortunately this doesn't appear to be the case and I hope with time you guys are able to work out any compatibility with the 4G model to benefit from the already terrific development that's going on with the 3.X kernel now.
I admire your guys' skills and look forward to all the improvements in store!
PS: I'd be more than happy to beta test anything you guys feel would address any compatibility issues on the TP 4G!
Click to expand...
Click to collapse
Do you think you can get me some dmesg and logcats??
Just sharing with you , if anybody is interested, a Beta version of MIUI for the OnePlus One.
I flashed it successfully on my International OnePlus One and am running it right now.
ALL CREDITS GO TO ID这么难么的个人空间 (miui.com developer). You can see the original thread here:
http://www.miui.com/thread-1849318-1-1.html
My changes :
- removed Chinese apps
- removed Sougou keyboard and Baidu apps
- added Sony Keyboard
- a few minor build.prop changes
- ROM is already rooted, the MIUI permission manager works perfectly
How to flash :
1. Download : MIUI 2.0 BETA
and copy to your phones storage
2. Download the Gapps package and copy to your phones storage
3. Unlock bootloader and acquire custom recovery from here: https://forums.oneplus.net/threads/guide-oneplus-one-how-to-unlock-bootloader-install-custom-recovery-and-root.64487/
4. Reboot into recovery
5. Wipe data, cache, dalvik cache and sytem
6. Install OnePlus_MIUI2.0_BETA.zip
7. Reboot your phone and setup the MIUI account
8. Restart back into recovery and flash Gapps
9. Wipe Cache and Dalvik
10. Reboot into system
11. Enjoy MIUI
Screenshots (Mega folder link)
Thank's to : http://techpunked.wordpress.com/
Just an FYI... On the latest TWRP this takes a long time to flash... waited almost 5 minutes for the flash to finish...
Yvan12 said:
Just sharing with you , if anybody is interested, a Beta version of MIUI for the OnePlus One.
I flashed it successfully on my International OnePlus One and am running it right now.
ALL CREDITS GO TO ID这么难么的个人空间 (miui.com developer). You can see the original thread here:
http://www.miui.com/thread-1849318-1-1.html
My changes :
- removed Chinese apps
- removed Sougou keyboard and Baidu apps
- added Sony Keyboard
- a few minor build.prop changes
- ROM is already rooted, the MIUI permission manager works perfectly
How to flash :
1. Download OnePlus_MIUI2.0_BETA.zip and copy to your phones storage
2. Download the Gapps package and copy to your phones storage
3. Unlock bootloader and acquire custom recovery from here: https://forums.oneplus.net/threads/guide-oneplus-one-how-to-unlock-bootloader-install-custom-recovery-and-root.64487/
4. Reboot into recovery
5. Wipe data, cache, dalvik cache and sytem
6. Install OnePlus_MIUI2.0_BETA.zip
7. Reboot your phone and setup the MIUI account
8. Restart back into recovery and flash Gapps
9. Wipe Cache and Dalvik
10. Reboot into system
11. Enjoy MIUI
Screenshots (Mega folder link)
Thank's to : http://techpunked.wordpress.com/
Click to expand...
Click to collapse
Beautiful, thanks!
Will download now..thanx !!
Sent from my One using XDA Premium 4 mobile app
livito said:
Beautiful, thanks!
Click to expand...
Click to collapse
Please don't quote OP...
Sent from my One using XDA Premium 4 mobile app
Why is this in General instead of Android Dev?
Nice to see more ROMs on the OPO.
Nice op, thank you. Have you tried going back to CM11S or restoring from a CM11S NAND backup? I'm just wondering if you ran any to any issues going back and forth between this rom. Thanks
My phone stuck at 1+1 logo,cannot boot with miui,,already tried flash using twrp & philz cwm..now revert back to cm11s
Sent from my One using XDA Premium 4 mobile app
It works perfect on my phone. I'm just curious how updates will be handled.
Sent from my One using Tapatalk
Sir,can u explain to me what recovery u use?u are using bacon or a0001?
Sent from my One using XDA Premium 4 mobile app
I'm using the official TWRP.
Sent from my One using Tapatalk
On OPO Global Version
TWRP 2.7.1.0
Stock Kernel
coming from CM11S, Smooth as butter no problems so far.:good:
---------- Post added at 11:04 PM ---------- Previous post was at 10:52 PM ----------
synergeticink said:
Nice op, thank you. Have you tried going back to CM11S or restoring from a CM11S NAND backup? I'm just wondering if you ran any to any issues going back and forth between this rom. Thanks
Click to expand...
Click to collapse
Did Nand Restore to CM11S, No problemo.:good:
zephiK said:
Why is this in General instead of Android Dev?
Nice to see more ROMs on the OPO.
Click to expand...
Click to collapse
It's because it's a repost of a ROM found somewhere else on the internet and not the work of OP himself, also the text of OP is copied from that blogpost he is referring to.
Nand restore works perfectly people !!!
Installed..works perfect.. Anyway to get the cm11s camera apk?
marliv said:
Installed..works perfect.. Anyway to get the cm11s camera apk?
Click to expand...
Click to collapse
Yeah. Just grab CameraNext.apk from Apps/Themes Section and install it normally. Worked for me.
I have one major problem with this ROM (and specifically with MIUI). I can't get Bluetooth working in my Ford Focus. I get it to intially connect, but then Bluetooth on the phone force closes. I've had issues with this in the past with MIUI, so I don't know how to fix it. :\
*edit*
Found the fix. Stupid easy.
Sent from my SM-T900 using Tapatalk
Nxpx said:
Nand restore works perfectly people !!!
Click to expand...
Click to collapse
After nand restore are you getting any errors with Wifi, my wifi connectivity is good but when i go into the wifi setting its FCing.
EDIT: Never mind, the FC problem was from something else.
darkjedi said:
I have one major problem with this ROM (and specifically with MIUI). I can't get Bluetooth working in my Ford Focus. I get it to intially connect, but then Bluetooth on the phone force closes. I've had issues with this in the past with MIUI, so I don't know how to fix it. :\
*edit*
Found the fix. Stupid easy.
Click to expand...
Click to collapse
I always think when people answer there own question its a good idea to post the fix, to help others with potentially the same issue.
darkjedi said:
I have one major problem with this ROM (and specifically with MIUI). I can't get Bluetooth working in my Ford Focus. I get it to intially connect, but then Bluetooth on the phone force closes. I've had issues with this in the past with MIUI, so I don't know how to fix it. :\
*edit*
Found the fix. Stupid easy.
Sent from my SM-T900 using Tapatalk
Click to expand...
Click to collapse
Could you share the fix with the rest of us?
---------- Post added at 12:46 PM ---------- Previous post was at 12:38 PM ----------
dansou901 said:
Yeah. Just grab CameraNext.apk from Apps/Themes Section and install it normally. Worked for me.
Click to expand...
Click to collapse
Thx..installed,works great.. Installed screencast also working good..if u want xposed use wsm tools
https://forums.oneplus.net/threads/rom-official-5-0-android-lollipop-alpha.223252/
ALPHA STAGE GUYS, EXPECT BUGS, MAKE A BACKUP IN RECOVERY BEFORE FLASHING!!
THIS ROM IS MADE BY ONEPLUS, NOT ME.
Here we go, official L for the oneplus one (made by oneplus) is here, there are a few bugs which can be found in the main link above.
Happy flashing!
And Happy new year!
All credit goes to oneplus. I'm just sharing the link!
It's not cyanogen mod though!It's an alpha build but no one at the OPO thread hasen't installed it yet!
Sent from USS Intrepid NCC-1631
---------- Post added at 07:22 PM ---------- Previous post was at 07:21 PM ----------
At least they are building their own rom!And happy new year guys!
Sent from USS Intrepid NCC-1631
I tried it but had an error about updater script. When i time i will try again
störte said:
I tried it but had an error about updater script. When i time i will try again
Click to expand...
Click to collapse
I haven't tested it yet, I'm not sure that I will. Cause of the bugs I am seeing on the OPO thread.
guys you need to unmount system before you flash otherwise the updater script will fail.
Great will retry
I'm using it right now. No real problems noticed so far except for a couple of crashes at first boot. It's really smooth. Pure AOSP.
Yes very pure.
Strange cant get into recovery anymore
Does anyone know if they're using the same sources as Cyanogen? (It had a weird name. CM started to suck when they started using it.)
Or is it PURE AOSP?
dugzino said:
Does anyone know if they're using the same sources as Cyanogen? (It had a weird name. CM started to suck when they started using it.)
Or is it PURE AOSP?
Click to expand...
Click to collapse
Pure CAF AOSP.
I can only recommend not to use it. My Recovery was deleted and i cant get into any Recovery anymore. I get only a chinese fastboot.. Tried to flash my Recovery via adb. On first boot it worked but then not anymore. So be very carefull
störte said:
I can only recommend not to use it. My Recovery was replaced and i cant get into any Recovery anymore. I get only a chinese fastboot.. Tried to flash my Recovery via adb. On firsat boot it worked but then not anymore. So be very carefull
Click to expand...
Click to collapse
Works perfect for me.
Thats strange. Anyway i flashed a recovery and deleted the system in order to restore a backup. It looks nice but the Recovery Problem must be solved in order for me to try again.
BUt i like the Wallpaper
störte said:
Thats strange. Anyway i flashed a recovery and deleted the system in order to restore a backup. It looks nice but the Recovery Problem must be solved in order for me to try again.
BUt i like the Wallpaper
Click to expand...
Click to collapse
I think you need to reflash recovery when you install it, which is easy to do from fastboot.
I did that. But even then i was not able to enter recovery
very very different modem, compared it against all the five I've got here (not all the previous modems) and can't see anything like it.
sha1 DD7A19EA09FF60485A6D8469F25C750A9AE627AE
md5 BA7C0A93BB63955408459ACA88BAAFFC
TeChNoC4AzY said:
I think you need to reflash recovery when you install it, which is easy to do from fastboot.
Click to expand...
Click to collapse
You would be correct. In fact, they specifically mention that in the instructions directly before Step 1.
This build does not have a built-in recovery
Click to expand...
Click to collapse
Well consider that it's build from their own source it's normal that it's asop-like but gonna give it a try tomorrow. Of course hope they will merge latest 5.0.3 that will come in these week and all other feature of cyanogenmod11S
confed said:
You would be correct. In fact, they specifically mention that in the instructions directly before Step 1.
Click to expand...
Click to collapse
rudi_j7 said:
guys you need to unmount system before you flash otherwise the updater script will fail.
Click to expand...
Click to collapse
How is that done?