So yeah, I've been using UrukDroid for a while now but I only just noticed that none of the camera apps (Camera, ZXing Barcode Scanner, Google Goggles) start up successfully. I've tried doing a full firmware reset in recovery mode, remove and reinstall SDE, and reinstalling Uruk, and noticed a few things.
-Stock: Works
-Stock with SDE installed (boot stock): Works
-Stock with Uruk installed (boot stock): Works *i think*
-Stock with Uruk installed (boot Uruk): Does not work
-Remove stock firmware + boot Uruk: Does not work
Does anyone know a solution to this? I'd really like to be able to use Uruk with camera working, it's the only method I have of having virtually unlimited space for apps in system storage.
Edited: I can't report a bug in the Uruk bug reports thread because this subforum is agraahdhsargh, don't tell me about it
Edited: Can $auron please add ipv6 support in UrukDroid? There's already an alternative zImage for chulri's root that has it, I'd really like to be able to use Google Goggles <3
A friend of mine (achosrocker) has the same probpem with his 43, but i dont have that poblem because im using a 101 without an HD cam..
So its only the camera of the 43
Can we get $auron to add support for the A43IT in the 2.3 update of Urukdroid?
Thanks.
ryadztu said:
Can we get $auron to add support for the A43IT in the 2.3 update of Urukdroid?
Thanks.
Click to expand...
Click to collapse
What update do you mean?
Currently we are on version 0.7, the next will be version 1.0
Maybe you meam the archos firmware update this week?
this is version is 2.3.20.
but i think if many people report this bug sauron and his guys will be fix this
Yeah, whichever version of uruk gets updated to 2.3.x, I'd like to have support for the A43's camera. (I'm not sure what kernel or android feature isn't compiled into uruk that allows the HD camera on the A43 to work).
If $auron is reading this, I would be willing to help do testing on my device if necessary.
Also, for some reason (I'm not sure if it's UrukDroid-related) every time my A43 reboots the mediascanner deletes all files under Documents, Music, Pictures, and Videos. It leaves the folders alone, although the respective apps seem to remove all traces of any files from their caches.
I get the same FCs on my 70IT with Uruk so it's not a matter of having a A43IT support I guess.
ryadztu said:
Yeah, whichever version of uruk gets updated to 2.3.x, I'd like to have support for the A43's camera. (I'm not sure what kernel or android feature isn't compiled into uruk that allows the HD camera on the A43 to work).
If $auron is reading this, I would be willing to help do testing on my device if necessary.
Also, for some reason (I'm not sure if it's UrukDroid-related) every time my A43 reboots the mediascanner deletes all files under Documents, Music, Pictures, and Videos. It leaves the folders alone, although the respective apps seem to remove all traces of any files from their caches.
Click to expand...
Click to collapse
You mean Android version 2.3.x?
For your other problem:
Please post in urukdroid bugs thread or send a pm to sauron
sibere said:
I get the same FCs on my 70IT with Uruk so it's not a matter of having a A43IT support I guess.
Click to expand...
Click to collapse
Oh really?
i dont heard about that problem once, but i have an idea:
Reinstall urukdroid over "normal" installation way or you wait untill 1.0 version and then you do the normal installation way, not the update way over **/UrukUpdate
Are you saying we all should reinstall UrukDroid, or just him? (And does "normal" mean the "easy" install option?) I for one would rather not have to reinstall from scratch unless absolutely necessary as I have a lot installed and configured and have even written a few changes to the system filesystem (new font, hosts file, etc.)
ryadztu said:
-Stock with Uruk installed: Does not work
Click to expand...
Click to collapse
Wait, I absolutely can't use things like the barcode scanner in UrukDroid (just force close the moment it tries to actually operate the camera -- though the initial startup with that information screen works fine, it FCs as soon as I hit the button to start the actual scanner part where it accesses the camera) but if I reboot to the stock firmware it works in that. Are you absolutely sure it doesn't work in your stock firmware? Really the stock firmware shouldn't even know if UrukDroid is installed or not, right?
Lennb said:
A friend of mine (achosrocker) has the same probpem with his 43, but i dont have that poblem because im using a 101 without an HD cam..
So its only the camera of the 43
Click to expand...
Click to collapse
Interesting. Do you suppose it could have a problem then with it being HD? Maybe the resolution or format causes a problem?
Nazo said:
1) Are you saying we all should reinstall UrukDroid, or just him?
2) Does "normal" mean the "easy" install option?
3) Do you suppose it could have a problem then with it being HD?
Click to expand...
Click to collapse
1) Just him, because he has an A70 and i've never heard before that problem on this device
2) Yap it means the easy install method
3) I suppose so, because i've never heard about this FC problem at Archos devi es except the 43 - the only device with a 720p cam...
@Nazo: By stock with Uruk installed I mean the stock Archos firmware and the SDE using the Uruk kernel are installed, but I boot UrukDroid. I'm not sure if it makes a difference whether UrukDroid is installed or not on when booting the Archos firmware.
Also, for some reason I can't get Uruk 1.0 or 0.7 to reinstall, when I try booting the SDE with the respective kernel replacement, I get the error "UrukDroid 1.0 ERROR: Failed to mount rootfs /dev/mmcblk1p2" which is the second partition on the internal storage, apparently. The stock firmware (latest 2.3.20 android 2.2) works perfectly fine with no problems.
They seem to have fixed this for urukdroid 1.0. I have a 43IT and experienced the same problems with 0.7. I was really worried that I wasn't going to have a camera anymore, but after upgrading, it works! Hallelujah!
This might be anecdotal, but for the first couple hours the device kept overheating and shutting itself off. I just turned it off for a good half-hour and it worked just fine.
Also, I think $auron made a way to reinstall urukdroid from scratch, instead of upgrading, which might fix your current problem. Look on the urukdroid thread (last post) / the wiki when it's updated.
same here..did not work before 1.0 and does work fine now.(using rc3 have not yet updated to 'real' 1.0 but should not make any difference)
I didn't even know there was a 1.0 already. It took me a while to find it, but I managed to. If I did the "reinstall" option hoping not to wipe out all of the programs I had installed and configured and all of their saved data it would still force close on startup. I had to do a fully reinstall from scratch. Now the barcode scanner works again. Unfortunately, I lost Weatherbug (instant force close on start) which was the only weather app I had left that didn't force close, so I'm not sure that this was worth it at all since that was far more important to me than the barcode scanner. At least I can run it if I reboot to the stock firmware, but this is kind of a pain. I guess I'm glad to see the barcode scanner working with the update even if I'd give it up to get any of my weather apps working again (I really don't feel like reinstalling yet again to downgrade though.)
Related
[size=+3]Honeycomb SDK Port - The Return [/size]
1. Introduction
So, for quite some time, we have had the excellent work done by deeper-blue, in porting the preview SDK, which whet our appetites for more Honeycomb to come. But despite Google allowing companies to ship Honeycomb devices, we have not had a source drop. As such, i felt like taking on the challenge of making the full SDK work on the nook; and now, here we are. This is build off the SDK 11 (rather than 10), and should be compatible with all real Honeycomb apps. Lets proceed.
2. Thanks & Credits
Before i go ANY further, i want to say thanks to whose people's work enabled and inspired me.
deeper-blue - It was your original modifications to the preview SDK that allowed me to get a BIG start on converting the full SDK. Honestly, i don't know how you figured out to do most of what you did, but it works!
dc13 - Your Asus Transformer system dump provided all the nice extra apps that are in use on this rom, in addition to the update framework. Thank you for your hard work!. http://forum.sdx-developers.com/eee-pad-development/ti-x-transformer-pad-v1/
rookie1 -Your dual boot Honeycomb script provided a great basis for a non dual booting script. http://forum.xda-developers.com/showthread.php?t=959461
I admit, i put together what i could with what i could find; if anyone is unhappy with what was used, please let me know and we can rectify the issue.
3. Installation
Not a whole lot to this one. Installation requires at least CWM 3.0.1.0. I am using internal CWM, so I will only certify it with that. I guess some people use CWM SD cards, but i am not sure how well it works with them.
Load the included .zip file on the SD card, and flash.
THIS WILL WIPE YOUR SYSTEM
DO NOT install this without having a good backup of Froyo or CM7.
DO NOT FORMAT BOOT
DO NOT INSTALL THIS WITHOUT HAVING A GOOD NANDROID BACKUP
Install take a few minutes, but once you are up, you will be greeted with the setup screen. Be sure to have a good Wifi around, it makes it easier to set everything up. Also, be sure to give the system a minute or two to settle when it first boots. Once you are all setup, you will be greeted with the full Android experience. Which leads me to my last bit of info.
4. Issues
Not working
- DSP (i think i jumped the gun on this one)
- From time to time, the screen may seemingly partially lock up. If this happens, please try to get an ADB logcat and post it here ("adb shell logcat > aFileName.txt"). A reboot will fix this issue.
- SD Card - RIght now, this is the big one. Not sure what about the framework change killed hte SD card, but i dont seem to see mine any more. If anyone has any ideas,lemme know
Working
SU (thank you racks11479)
SetCPU (and all other root needing things)
Audio (thank you deeper-blue)
3D
WiFi
Market (thank you PatF, et al)
Calendar (thanks Rockwig)
Gmail
- To kill the flashing red box (thank you mazook98): http://forum.xda-developers.com/showpost.php?p=13504316&postcount=109
(and more)
5. Community
So, what to do from here? Well, i will keep doing what i can, but i am by no means an expert. I invite anyone and everyone whom could possibly help make this better. If you think you can get Root or Market working - dont even ask; grab the code and mod away. If you have any advice, please share it. Android is so amazing because of the community.. lets keep it that way!
6. Links & Releases
5/9/11[/b]
This link represents a new phase of the Honeycomb build. I have adapted the framework from the posted eee Pad V3 build (linked in section 2). I feel this is a huge step up in UI, and a good push towards a daily driver. The UI is still a bit laggy, but it isn't too bad. Again, it wont be perfectly fixable until we get the source, but for now, its coming along.
Honeycomb Hybrid - RC1
http://www.multiupload.com/71K84XF6BF
Updated ramdisk made by Racks11479, that will allow SD mounting
See: http://forum.xda-developers.com/showpost.php?p=13698333&postcount=483
http://www.multiupload.com/3D9WSPUAUZ
**** ARCHIVED: DO NOT USE *****
Honeycomb SDK - RC3
RC3 Brings in the Calandar fix (thanks Rockwig), and a new build.prop (thanks xboxexpert), as well as some cleanup.
http://www.mediafire.com/?z6a2x97hlr5ve8p
Honeycomb SDK - RC2 (thanks to declain for creating an updated rollup)
RC2 brings in the fixed SU, Market, and Audio, all in one neat package!
https://rapidshare.com/files/460775452/update-HC-rc2.zip
Honeycomb SDK - RC1
http://www.mediafire.com/?czghefkha5zetab
www.unvisible.org/files/update-HC-rc1.zip - Thanks luciferii!
Su to push to allow Superuser (thanks for the info racks11479):
http://forum.xda-developers.com/showthread.php?t=953110
**Note, if pushing to xbin does not work, push the file to bin, and also set the perms there. That got it working for me**
6a: Change Log
RC3 - 5/6/11
- Fixed Calendar
- Updated build.prop
- DPI set to 140
- Installer no longer wipes out data; all future revisions will leave user partitions alone
- Cleaned up some unneeded programs
RC2 - 5/5/11
- Fixed SU
- Fixed Sound
- Fixed Market
RC1 - Release
7. Questions and Answers
With the stock Market still being funky, what options do i have?
The system can still side load apps, so any APKs you can grab can be installed with adb. Additionally, because of this,you can install other 3rd party Markets such as Slide and Amazon, which will let you install more apps.
Can i use the HC overclocked kernel?
At this time no. I have tried using the last released HS OC kernel, and something about it causes the system to hang at the boot animation. I want to look into it further though, and see if i can discover the source of the issue.
As of RC1, the kernel shipping in this package, is the same one that is found in the "HC-v4-emmc-2nd-edition" released for the preview SDK.
What is different about this release, compared to the other SDK port
The previous port was based off of the preview SDK, which Google labeled as SDK 10. The actual release of Honeycomb however, was bumped to SDK 11. This port uses that code, which means that it should be compatible with all the new new Honeycomb apps (Google body, etc). Certain things, like the Gmail for tablets, do work, and show what Honeycomb is all about.
How much more can be done on this release?
From here, the big fixes would be:
- Getting the stock Honeycomb Market to work
- Getting audio working
- Getting newer OC kernels workin
- Smothing out the UI experience as much as possible.
How can i help?
All the source that i had available is in the .zip package. Because there is no freely available source, all the work involves modifying the released binaries and framework .jars. There is additional tweaking that can be done to the ramdisk and kernel. If you feel adventurous, all of these are in the update package, and can be tweaked at your leisure. If you think you have something, don't be shy - zip it up and let us test it!
Oh, make sure you are signed in your Google account. Reboot, check for market.
Sent from my Samsung-SPH-D700 using XDA App
marcusant said:
Oh, make sure you are signed in your Google account. Reboot, check for market.
Sent from my Samsung-SPH-D700 using XDA App
Click to expand...
Click to collapse
If not, adb push zeam and try flashing cm7 gapps.
Sent from my Samsung-SPH-D700 using XDA App
marcusant said:
If not, adb push zeam and try flashing cm7 gapps.
Sent from my Samsung-SPH-D700 using XDA App
Click to expand...
Click to collapse
Gave it a try - no go. Lots of force closes going on...
I am soooo looking forward to this. No matter how great the other roms are. I just love the Honeycomb UI. Downloading now and will play around with it and hopefully will be able to contribute in someway.
Thanks,
Racks
Thanks for working on this! Hopefully the issues can be fixed soon enough.
I will poke around with it also. I ran EMMC v2 for a long time and the HC UI was just so smooth.
Thanks Madcat for taking this on.
I know this was meant for EMMC. But I just prepped and installed this to my SDcard rom and boy do I loves me some honeycomb. I assume you are aware of the red border issue? Or might it be because i'm running it off an SDcard. Don't mean to throw things off with the SD install.
Thanks,
Racks
racks11479 said:
I know this was meant for EMMC. But I just prepped and installed this to my SDcard rom and boy do I loves me some honeycomb. I assume you are aware of the red border issue? Or might it be because i'm running it off an SDcard. Don't mean to throw things off with the SD install.
Thanks,
Racks
Click to expand...
Click to collapse
Aye - i am aware of the boarder, and didn't remember if there was a way to turn it off.. It was way too long since i messed with HC...
thanks dm for getting hc back into life, im sure there will be many people come out of the woodwork to help with this, it seems like youve got it mostly there. once it gets market i will be all over this
insaneturbo13 said:
thanks dm for getting hc back into life, im sure there will be many people come out of the woodwork to help with this, it seems like youve got it mostly there. once it gets market i will be all over this
Click to expand...
Click to collapse
Hey insaneturbo13 . Did realize you were a NC owner too .
@Divine_MadcatI'm hoping to come into some free time soon, and should be able to test and contribute where i can.
Thanks,
-h8
h8rift said:
Hey insaneturbo13 . Did realize you were a NC owner too .
@Divine_MadcatI'm hoping to come into some free time soon, and should be able to test and contribute where i can.
Thanks,
-h8
Click to expand...
Click to collapse
hey yea, im now a regular here, good to see a familiar face haha
owned one of these puppies for about a month now
OK, just flashed CM7 latest Gapps. Market shows up. Signed in. Can browse. Search. But unable to install any apps.
Error I'm receiving is Google Services Framework (process com.google.process.gapps) has stopped unexpectedly.
I can install backed up apps by pushing via ADB and through a File Manager
Awesome ROM! Many people will be happy to see HC development move forward.
I was able to flash this using the SD card I use to flash CM7. I had a few keyboard FCs that was stopped when I specially picked US english. Glad to see wireless working, and the SD card slot works. Nook encoded videos play poorly, but I can't tell if its the DSP or the lack of audio. Interesting to see the differences between the final SDK and the one we had previously.
Thanks again!!!
well im currently giving it a try. Like you said, market doesn't show up but i saw that in my notification bar it said that i had updates. I clicked on it and it took me to "my apps" and installed all my paid for apps just fine . I'm not able to get to the rest of the market though.
Thank you
Many thanks Divine , Have been waiting for this for a long time. love the widgets.
I am interested in this, carry on
The amazon app market works fine.
Just a random Q, but has anyone tried these?
http://nookdevs.com/Honeycomb_Google_Apps_and_Market
http://forum.xda-developers.com/showthread.php?t=941445
Hi all,
I have a mini pro/U20i running Eclair, specs as follows;
Firmware: 2.1-update1
Baseband: M76XX-TSNCJOLYM-53404006
Kernel: 2.6.29
Build no: 2.0.A.0.504
Rooted, xrecovery installed
I'm looking to upgrade to the latest stable android version available for my phone, but must admit the in-depth tech talk does go over my head a little when looking at the ROM threads. I have enough tech savvy to be able to flash etc, but not too great with the programming speak.
I'd like to ensure that bluetooth, wireless, root, gprs etc are all 100% working on the ROM I upgrade to. Not bothered about radio or anything you can get an alternative of from the market.
From what I've seen gingerbread is available but not yet 100% functional, and I know there are stable Froyo versions available however the requirements state the baseband as above, but ending in 53404015 is required.
Is there considerable risk flashing a ROM if my baseband is slightly different?
I'm particularly looking for stable multitouch too, but the thread I read says manual edit of .sh and .prop files must be done - and I don't know how to do this
Dev and user opinions would be muchly appreciated.
Hi you will need the newer baseband just update with seus then you will need to reroot and install xrecovery again then once you have done that go to this thread ( http://forum.xda-developers.com/showthread.php?t=1059361 ) its the most stable I think and dual touch is included so no messing around
Hope this helps you
Sent from my U20i using XDA App
just use the flasher and baseband files from the baseband thread. much faster and easier than using seus and rooting again. just put the rom you want on with xrec, pull the battery out, flash, and youre done! shouldnt take more than 10 minutes once you know what youre doing!
For me, using SEUS is safer, even if I have to root and install xRecovery again.
I you want the most stable ROM with all functions working, you have to choose CM6-MiniCM hybrid noOC from Slade.
I'm using that ROM since he released it and never had a reboot, and everything is working.
If you have stock rom, you should format SD card.
Temes
temes said:
For me, using SEUS is safer, even if I have to root and install xRecovery again.
I you want the most stable ROM with all functions working, you have to choose CM6-MiniCM hybrid noOC from Slade.
I'm using that ROM since he released it and never had a reboot, and everything is working.
If you have stock rom, you should format SD card.
Temes
Click to expand...
Click to collapse
yeah using SEUS is better... and you can reflash after you update using it....
after root and xrec, just make a backup on xrec so you can reflash to 2.1 back... and dont waste time on reflash+root+xrec again.... i did that save lots of time
ps: make sure full wipe+dalvic clear before restore backup... ^^
riesan said:
after root and xrec, just make a backup on xrec so you can reflash to 2.1 back... and dont waste time on reflash+root+xrec again.... i did that save lots of time
Click to expand...
Click to collapse
Yeah, I did it too, but never needed that backup I flashed with SEUS last, when I first updated to slade's ROM
Temes
Cyanogen Froyo CM6-Latest (based on MiniCM/CM6v2) - v2.0 + DualTouch is the most stable ROM for me. Just flash using SEUS or flasher to get the required baseband.
I recommend using the flasher because it helps you understand the flashing process. Just follow the tutorial.
Thanks for all your help guys, that's helped me out no end
I am now the proud owner of an x10mp android 2.2.1 (went with Slade's ROM - big thumbs up, it's beautiful!!)
I have one final question.. when I installed the last ROM I had, I used flashtool, so doing it with xrec was a new experience for me... I did notice that before it installed the rom, it said 'formatting /system' or words to this effect.
I need to install the two hotfixes that are posted with the rom - the drain and browser ones... do I package the files within these zips into an update.zip and run again from xrec or can I transfer the updated system files just using root explorer? I'm worried that xrec will take the update.zip as a full rom and will delete the contents of my system folder - please reassure me this isn't the case and it will just update with newer files!
MANY thanks again for your help and advice!
kao_u20i said:
Thanks for all your help guys, that's helped me out no end
I am now the proud owner of an x10mp android 2.2.1 (went with Slade's ROM - big thumbs up, it's beautiful!!)
I have one final question.. when I installed the last ROM I had, I used flashtool, so doing it with xrec was a new experience for me... I did notice that before it installed the rom, it said 'formatting /system' or words to this effect.
I need to install the two hotfixes that are posted with the rom - the drain and browser ones... do I package the files within these zips into an update.zip and run again from xrec or can I transfer the updated system files just using root explorer? I'm worried that xrec will take the update.zip as a full rom and will delete the contents of my system folder - please reassure me this isn't the case and it will just update with newer files!
MANY thanks again for your help and advice!
Click to expand...
Click to collapse
Just use each from xrec, it will replace some file but it won't format your system, only the big release file does that (100MB++).
hansip87 said:
Just use each from xrec, it will replace some file but it won't format your system, only the big release file does that (100MB++).
Click to expand...
Click to collapse
It depends what formatted, deleted or owerwrited on update script. Don't worry, slade knows what he's doing
Anyway DON'T TRY TO FORMAT YOUR SYSTEM WITHOUT INSTALLING NEW ROM!!!
Just always follow install notes and everything will be fine.
Temes
Right then, an update (excuse the pun!)
I followed SEUS to get the xx 4015 baseband
I flashed Slade's noOC rom and then hotfixes using xrecovery
I now have a happy 2.2.1 android mini pro with multitouch!
At first, it was a little slow and I had a few blank screens and FCs....
Screen brightness was very low even when I was actively using the phone, so I unchecked the auto display option and set a brightness I'm happy with. Sorted!
With Titanium I restored my backups, including my wifi connections. Saves having to re-enter all the passwords right? Wrong!
I had a number of connection issues. Data was very slow, to slow to even register my google account on market. Wifi wouldn't load market or bring up anything in the browser...
When I did establish a fast enough data connection, market was completely out of sync with my phone apps.
Turns out the data connection just needed to 'warm up' along with the new android system. As for the wifi, I removed all my connections with the 'forget' option, and manually scanned and entered the passwords again. Now my wifi flies
So all in all, a very smooth upgrade process, a couple of hiccups with the data/wifi and brightness that have been ironed out, and now I am loving my new android again. The multitouch is very slick and having superuser, jit and xrec preinstalled is just brilliant! Games are lag free too which makes a big difference (yep, I'm an Angry Bird club member)
Think I've made my iphone user hubby a bit jealous. I like to remind him every now and then that apple have him by the balls, and he has to buy a whole new phone to do any update such as the one I've just done (again )
The battery drains a little quicker than on the previous rom, but I expect that will settle down after a few days. One thing I have noticed is that I'm repeatedly ending apps with ATK that I hadn't even opened - on my last rom I'd never see anything that I hadn't opened myself.
An example being, just opened ATK and I have the following running;
APN OnOff
Gmail
Maps
None of these I've opened since I last ran ATK Other repeat offenders are Browser, google search and camera,
Any ideas? WhatsApp used to open randomly until I moved it to the SD card. It's behaving itself now.
Don't need to use taskkillers in 2.2.1, android handles battery quite efficiently.
Battery increase is due to overclocking and because it's a custom rom.
Hope that helps.
XDA ♥
My battery life has stabilised now. Took phone off charge about 8.30 am and now, 1.30pm it's at 83%, so can't complain
I find apps such as maps and google voice/search do drain the memory quite a bit so still prefer to use atk. Just opened atk to find I have;
maps
handcent
apn OnOff
gmail
google voice
ROM manager (I've never opened this since installing the rom)
calendar
camera
all running and memory at 41M. Killed apps and memory now at 71M
Is there a way to stop these apps from randomly running? Apart from a calendar alert for today, I haven't manually opened anything from the list
cheers,
K
Sorry for ignorance:
Can I flash a rom and do all the nec. stuff from Ubuntu? Or will I need Window$ to flash a mini pro?
kao_u20i said:
My battery life has stabilised now. Took phone off charge about 8.30 am and now, 1.30pm it's at 83%, so can't complain
I find apps such as maps and google voice/search do drain the memory quite a bit so still prefer to use atk. Just opened atk to find I have;
maps
handcent
apn OnOff
gmail
google voice
ROM manager (I've never opened this since installing the rom)
calendar
camera
all running and memory at 41M. Killed apps and memory now at 71M
Is there a way to stop these apps from randomly running? Apart from a calendar alert for today, I haven't manually opened anything from the list
cheers,
K
Click to expand...
Click to collapse
It's normal to have applications taking up memory. It is so that it will be speedy in opening those apps so try not to use a taskkiller. The only time these idle apps use battery is when there is CPU usage: so check with your spare parts. If they don't use CPU, no need to kill.
If you're insistent that the apps are frustratingly persistent, then freeze the app using titanium backup. Note that freezing certain system apps may cause problems eg freeze google talk and market won't work.
Try at your own risk.
XDA ♥
Can i get the link to ''CM6-MiniCM hybrid noOC'' Thanks
Q&A: [ROM-1.2/GRJ90] CM7Tab for the GTab (based on CM7 Nightlies) [Update: 08-15-11]
MOD EDIT: THIS IS THE Q&A SECTION FOR [ROM - 1.2] CyanogenMod 7 nightlies for the GTab
ALL Q&A FOR THIS ROM HAPPENS HERE.
Thanks.
---------------------------------------------------
As suggested, I have decided to make my own thread for the Cyanogenmod nightlies and other ROMs. It will make things a lot easier in the long run.
Disclaimer: as with the other Roms, Use at your own risk! Since the CM7 nightlies are basically an ongoing beta, you run the risk to brick your Gtab if you are not careful. Use to learn NxFlash first before attempting to flash ROMS. Also, do yourself a favor and get Titanium Backup! Always backup yours apps/settings and wipe data/cache/dalvik before flashing.
These will be using the bootloader's 1.2 Pershoot's kernel (2.6.32.43 / 1.4 ghz Kernel) for GB. This ROM works with the Gtab and should work with the ZPAD altough I have no confirmation of this yet.
Thanks goes out to: Team Douche/Cyanogenmod Devs for making a great ROM, Zyhong for showing me how to update to 1.2 and a few more tricks, Maxdamage for taking the time to compile the nightlies for 1.1 users, Pershoot for making such a great kernel and Roebeet for being the one that inspired me to take my journey down the Android rom lane.
1) latest version of CM7Tab: CM7Tab build 08082011 (Nightlies changelog)
2) Test CM7Tab with 4950 drivers: Test Build 08152011
Changes in modified version
1- replaced DSPmanager.apk with a previous version that is known to work (7.0.3) (if you open it, it FCs)
2- vold.fstab is setup as sdcard for internal storage & emmc for external card
3- using pershoot's 2.6.32.43 GB kernel for 1.2 bootloader (For more info, check his blog.
4- Read_ahead_kd increased from 128 to 2048.
5- Set up overclocking by default and battery saver script + cpu governors via userinit.sh (from Zyhong's ROM, based on Caulkin's scripts).
6- Replaced Camera libs & apk to stop the 8-bit pixelling.
7- Increased dalvik.vm.heapsize to 64m (07102011)
8- Set some values to improve video playback (07272011)
9- Changed values for lowmemorykiller minfree in init.rc (08072011).
10- changed EMMC to microsd (08072011)
11- updated ROM up to 2.3.5 (08072011)
12- Camera fix (08082011)
To-do list:
1- remove some apks (such as Rom manager) & create a removed apks folder.
--------------------------------
Issues:
1) Once you set up DSPmanager, it force crashes.
1) Vanilla CM7 nightly (only vold.fstab was modified): Latest build: Build 07262011 (Changelog)
If you have suggestions/ideas, do not hesitate to share them.
thank you.
Going to give it a try, tried cm7 a while ago and was great with it but seemed a bit slow. On Iluminate now do I have to flash back to stock?
Sent from my Android Illuminate using XDA Premium App
nelomen said:
Going to give it a try, tried cm7 a while ago and was great with it but seemed a bit slow. On Iluminate now do I have to flash back to stock?
Sent from my Android Illuminate using XDA Premium App
Click to expand...
Click to collapse
How long ago did you try it? I try to play areound with CM7 with the CM7tab ROM to see if I can speed it up a little as well. You can give it a try and tell me what you think.
Icewyng said:
As suggested, I have decided to make my own thread for the Cyanogenmod nightlies and other ROMs. It will make things a lot easier in the long run.
Disclaimer: as with the other Roms, Use at your own risk! Since the CM7 nightlies are basically an ongoing beta, you run the risk to brick your Gtab if you are not careful. Use to learn NxFlash first before attempting to flash ROMS. Also, do yourself a favor and get Titanium Backup! Always backup yours apps/settings and wipe data/cache/dalvik before flashing.
These will be using the bootloader's 1.2 Pershoot's kernel (2.6.32.42 / 1.4 ghz Kernel) for GB. This ROM works with the Gtab and should work with the ZPAD altough I have no confirmation of this yet.
Thanks goes out to: Team Douche/Cyanogenmod Devs for making a great ROM, Zyhong for showing me how to update to 1.2 and a few more tricks, Maxdamage for taking the time to compile the nightlies for 1.1 users, Pershoot for making such a great kernel and Roebeet for being the one that inspired me to take my journey down the Android rom lane.
Issues:
1) Once you set up DSPmanager, it force crashes.
1) Vanilla CM7 nightly (only vold.fstab was modified):
Latest build: Nightly build 07112011 (Changelog)
2) Modified version of the ROM: CM7Tab build 07102011
Changes in modified version
1) replaced DSPmanager.apk with a previous version that is known to work (7.0.3) (if you open it, it FCs)
2) vold.fstab is setup as sdcard for internal storage & emmc for external card
3) using pershoot's 2.6.32.42 GB kernel for 1.2 bootloader (For more info, check his blog.
4) Read_ahead_kd increased from 128 to 512.
5) Set up overclocking by default and battery saver script + cpu governors via userinit.sh (from Zyhong's ROM, based on Caulkin's scripts).
6) Replaced Camera libs & apk to stop the 8-bit pixelling.
7) Changed values for lowmemorykiller (07102011).
8- Increased dalvik.vm.heapsize to 64m (07102011)
RC1 version of the rom with changes: 7.1.0 RC1 with Pershoot 42 kernel
(Sorry if this is short but I will improve the thread as it goes)
To-do list:
1) remove some apks (such as Rom manager) & create a removed apks folder.
2) change the EMMC to Sdcard2
If you have suggestions/ideas, do not hesitate to share them.
Click to expand...
Click to collapse
personally I have been using your build for a while and quite happy with it except the market which sometime shows my apps and other time it doesn't. I have not tried any market fixes yet, so it is partiality my fault as well.
Icewyng said:
How long ago did you try it? I try to play areound with CM7 with the CM7tab ROM to see if I can speed it up a little as well. You can give it a try and tell me what you think.
Click to expand...
Click to collapse
I tried it today but was getting a lot of fc's, it did seem a little faster then I remember except the boot up was really slow as I remember. I did not give it a full try because I failed to wipe everything because I was at work and wasn't really supposed to be on it. I will do it again tonight with full wipe and see if it gives better results and let you know.
I just realized you have a tab build so I will try that one. The one thing I noticed right away with cm7 is that my tablet looked like a phone and I have been jumping around from HC roms and got used to a more tablet specific rom. I will give you update in a few hours I think.
Edit: have been trying for a couple of hours now but sent me in to boot loop had nvflash back to stock, will give it another shot once this silly Tap n Tap is finished loading.
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
rob_z11 said:
personally I have been using your build for a while and quite happy with it except the market which sometime shows my apps and other time it doesn't. I have not tried any market fixes yet, so it is partiality my fault as well.
Click to expand...
Click to collapse
Dalingrin was kind enough to provide a fix that seems to resolve most of the problems with market (including buying apps). It was merged in build 07092011+ so give it a try and tell me how it goes.
nelomen said:
I tried it today but was getting a lot of fc's, it did seem a little faster then I remember except the boot up was really slow as I remember. I did not give it a full try because I failed to wipe everything because I was at work and wasn't really supposed to be on it. I will do it again tonight with full wipe and see if it gives better results and let you know.
I just realized you have a tab build so I will try that one. The one thing I noticed right away with cm7 is that my tablet looked like a phone and I have been jumping around from HC roms and got used to a more tablet specific rom. I will give you update in a few hours I think.
Click to expand...
Click to collapse
The FCs you were getting were probbly from DSPManager. It is a known issue that seems to come from a "broken pipe" in one of the libs. For now, it is best just to remove it.
For the bootup, someone suggested moving apps to the SD card. Apparently, it would speed up the process.
I am conscious that 2.3.4 is made with phones in mind but it is a step up from Froyo and having partial hardware acceleration helps.
Just tried again and got stuck on CM7 logo boot loop, this was with the CM7 tab build. did full wipe of cache, dalvik, and user data. Not sure what happened. Restoring to Illuminate rom if you have some ideas on how or what else I can do to try this rom let me know.
Hey there Ice.
First off, awesome work on this and thank you for taking the time.
I would recommend editing the build.prop file to set the Manufacturer to HTC. This fixes the playback issue with Netflix (Chipmunk). I tested this out fully on my gTab last night and it's the ONLY setting that needs to be modified. Aside from that, everything seems to work.
Good work!
Hi
Has anyone tried installing volume+ on this rom? I'm on BL1.1 CM7 rom but volume+ does not install. If this works, I'll take the bold step to upgrade to BL1.2.
I don't know if it's just my hardware. My gtab's speaker is very soft and I want to try cranking it up with volume+ (which works on my phone running cm7).
thanks a lot.
DroidTV phone size not full screen....Anyone have other apps that did that after....
I was using DroidTV, and it was full-screen and then rebuild my G Tab with the cm7tabl-0710200-1.2 and when I reinstalled DroidTV it is now phone size display on the G Tablet.
I used Titanium Backup to restore the app and the settings. Anyone have issues like this with an app that did that after re-installing after a full rebuild? Any build.prop setting or somewhere I could check?
Thanks. Steve.
Thanks everyone for your feedback.
@Mike: I have heard of this before and wasn't sure if anyone would be interested in it. I will change that on the CM7Tab version in the next few days.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
@Artful: I will look into this. It might just be that the rsolution isnÈt set right. I will let you know how it goes.
Icewyng said:
Thanks everyone for your feedback.
@Mike: I have heard of this before and wasn't sure if anyone would be interested in it. I will change that on the CM7Tab version in the next few days.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
@Artful: I will look into this. It might just be that the rsolution isnÈt set right. I will let you know how it goes.
Click to expand...
Click to collapse
Thanks Ice. Other than that I have yet to find any major issues that in the build.
Other than apps that open portrait only with the bottom on the side with the power button. Tried to say to not rotate 90 degrees but they still open that way Apps that open landscape then won't rotate to the 90 degree position but portrait apps still open that way
This is the most stable I have used and performance seems good. A co-workers has the same build, I installed it for them since they are techie-challenged, and theirs is turtle slow because I think they have Skype running all the time.
Icewyng said:
Thanks everyone for your feedback.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
Click to expand...
Click to collapse
sorry for not being clear. I did not mean pressing the volume+ button. i actually meant this app to boost the volume of gtablet.
http://forum.xda-developers.com/showthread.php?t=1023433
I guess the app has dependencies on dsp manager, that's why it did not work on my B1.1 cm7. Since you have replaced the dsp with a workable one in your rom, I would like to check if the volume+ app works here.
Appreciate your work on the rom!
vhendsume said:
sorry for not being clear. I did not mean pressing the volume+ button. i actually meant this app to boost the volume of gtablet.
http://forum.xda-developers.com/showthread.php?t=1023433
I guess the app has dependencies on dsp manager, that's why it did not work on my B1.1 cm7. Since you have replaced the dsp with a workable one in your rom, I would like to check if the volume+ app works here.
Appreciate your work on the rom!
Click to expand...
Click to collapse
Actually, I think it has more to do with a problem with one of the audio libraries. I did a logcat and it seems something called AudioFlinger can't set a parameter properly.
If anyone can fix this, I can send the logcat to help out.
I wanted to apologize for not being able to upload the new nightly today. I had to rebuild my computer and took the opportunity to switch to a new Linux distro. Just tested the new system and all is great.
I will post Build 07172011 later this morning.
Where are the nightly's getting posted now? Thanks and this is the most stable MOD I've had on my G Tab.
Do video apps work as far as no rotation with Oovoo, yahoo, reelportal, etc? Audio work okay with chatting?
mirrors:
http://dev-host.org/cops0ujuwmm0/update-cm-7.1.0-smb_a1002-07182011-1.2.zip
http://dev-host.org/8xjvaysomd1i/update-cm7tab-07102011-1.2.zip.zip
-deck
I have Vegan-tab gingerbread 7.0RC1 pershoot bl1.2.
Flash no longer shows up on my installed apps. When i search for it, It says it is not compatible for my device, google maps does the same thing too. Does anyone else have this problem too. I just noticed it last week.
miggyg said:
I have Vegan-tab gingerbread 7.0RC1 pershoot bl1.2.
Flash no longer shows up on my installed apps. When i search for it, It says it is not compatible for my device, google maps does the same thing too. Does anyone else have this problem too. I just noticed it last week.
Click to expand...
Click to collapse
Yeah, that was the only problem I had with that ROM. It seemed to always happen for me when the tablet would hard freeze and I had to reboot. Once it boots back up, anytime I access the Market, everything was not compatible with GTab.
I never found a solution other than returning to HC. It was a good ROM and that was the only prob I had with it.
Does [BL1.2]VEGAn-TAB GingerEdition v7.1.0 solve this issue?
Yes, it is much better running Vending 3.1.3.
If you have superuser rights, use AntTek App Manager to backup flash, than delete it from system (even sys application version), the Hulufied version from ASOP Ginger posts. You might need to install, update from market, remove, and install Hulufied version to stick.
Just download it on the PC..then hook up your GTab to the PC...drag the Flash 10.3 (Yes that one will work) into the storage on the device. Then download it from there.
All the apps (And there was ALOT) that shows up Non Compatible with your device in the Market...will actually work if you do it that way.
Thank you for all the responses. I went for the upgrade option to Vegantab 7.1. I am very pleased.
--> BACK UP ANDROID AND WEBOS!! <--
Get it before server gets hammered. I removed all patches and set the default kernel just in case.
About webOS 3.0.5
Software update information and release notes for TouchPad (Wi-Fi)
Article ID: 18666
This article lists new applications and feature changes in software updates for the TouchPad.
The HP webOS 3.0.5 update enhances core apps like Email and Calendar, improves the video calling experience, and fixes additional bugs.
* Faster switching between Day, Week, and Month views, and faster event display in Calendar.
* Faster scrolling when reading an email message.
* Email attachments are now saved with draft messages.
* Added sender photos and IM presence indicators in Email.
* Improved stability when watching video in the Web app.
* Improved handling of MP3s that are transferred from a computer using USB Drive mode.
* Added a dedicated view of contacts available for a video call, for quicker setup of a video call.
* New alert when video quality might be lower because of network issues.
* When typing, pressing the space bar twice inserts a period. This can be toggled on and off.
* Auto-correction can be turned off directly from the onscreen keyboard.
* Added support for HTTP Live Streaming.
--> BACK UP ANDROID AND WEBOS!! <--
Does the update do anything to my CM7 partition or is it safe to update?
someone over in the webOS forums said it installed fine and didn't mess up cm7. I'm actually posting from webOS and downloading as we speak, so I guess I'll see in a few minutes.....
Moboot might be be removed just like the previous upgrade. if so..
http://liliputing.com/2011/10/hp-releases-webos-3-04-for-the-hp-touchpad.html
yeah, I just reconsidered my decision to install it. With ICS being close, I don't wanna get stuck in webOS. I'll just wait and see what happens....
I have updated and it has left moboot 0.3.5, cwm and xron all intact.
vinscuzzy said:
yeah, I just reconsidered my decision to install it. With ICS being close, I don't wanna get stuck in webOS. I'll just wait and see what happens....
Click to expand...
Click to collapse
Your device will be fine. I've been through like 3 3.0.5 updates already and they all keep moboot. If it does erase it, just reinstall moboot alone with acmeinstaller and your CM data and everything will still be intact.
if the update throws an error: remove all patches, uninstall custom kernel, remove/uninstall any visual enhancements, open Preware and install "emergency patch recovery", Doctor. All in that order but not necessarily all of them.
http://palm.cdnetworks.net/rom/touchpad/p305rod01122012/wd305wifi/webosdoctorp305hstnhwifi.jar
updates
So, I just updated both my TouchPads.
The one with stock WebOS 3.0.4 (no android at all), installed the update with no issues. I did disable (not uninstall) the UberKernel to PalmDefault prior to update and it worked fine.
The other one, which I had XRON 2.9.1 loaded, failed the first attempt. I had disabled (same as the other one) the UberKernel but that did not help. So I uninstalled the kernel and the second attempt seems to work fine. I installed the kernel again once the update was completed.
One with the XRON also had the latest UberKernel where as the stock one had an older version loaded. I am not sure what difference that makes, but that is what I experienced.
They are both using the latest UberKernel and all seems fine.
Android components (moboot & cwm) are left intact after the update.
edit... spoke to soon. I am stuck in a bootloop. I am attempting to reflash the XRON 2.9.1 and see if that brings it back. I am however able to see moboot and CWM loads and works fine. I am reloading the rom via CWM as I type... I can see the bootanimation... and... android lives again... ^_^
Everything went smoothly with update no problem here moboot & cwm keeps intact
WebOS certainly feels more responsive and fluid
when I click install now, it reboots to moboot and when I choose webos, it doesn't install
slick_shoes said:
when I click install now, it reboots to moboot and when I choose webos, it doesn't install
Click to expand...
Click to collapse
same here. Tried to remove patches and Themes, but no luck =/ Will try everything else i can do, then use doctor
So I removed all of my patches before updating and now after updating when I look in pre ware there are no patches and when I search for them none show up. Is this because the patches are not compatible with the new version yet? Or is there something I am missing? Thanks!
Help please!
So i guess I messed up. I thought I only had to uninstall uber kernel after an installation error. That isn't the case. Now I no longer boot into moboot at all and the screen just stays at www.palm.com/ROM. What do I do now and is there a way I can get to/restore the android operating system without losing it? What will happen when I webos docter it? Will it erase my partitions?
such an idiot
I'm such an idiot, I just saw the update and I clicked download and install without checking the forums first.
none of my patches work now, and i've lost my overclock. do I just need to wait until the patches are re-released or do I need to do something else, also how do I ,get overclock back? will thus fix itself when the patches re-release?
I'm totally lost.
fraz82 said:
I'm such an idiot, I just saw the update and I clicked download and install without checking the forums first.
none of my patches work now, and i've lost my overclock. do I just need to wait until the patches are re-released or do I need to do something else, also how do I ,get overclock back? will thus fix itself when the patches re-release?
I'm totally lost.
Click to expand...
Click to collapse
You are correct, give yourself some credit. The patches will be updated and should say update under preware when available.
Not everyone is ready to release updates the same day as HP. So give them a few days and they should update. Possibly longer.
Sent from my HTC HD2 using Tapatalk
my touchpad was also bootlooping, I was freaking out. Uninstalling android diddn't help, and trying to reflash moboot failed to. The only thing that worked for me was to use Webos doctor. I guess il'l reinstall android on the touchpad when ics comes out.
Tarrance17 said:
my touchpad was also bootlooping, I was freaking out. Uninstalling android diddn't help, and trying to reflash moboot failed to. The only thing that worked for me was to use Webos doctor. I guess il'l reinstall android on the touchpad when ics comes out.
Click to expand...
Click to collapse
OK i didn't get an answer so I went through with the doctor repair. It worked! Then I went about putting android back on. I did that and to my surprise, when it booted my newly installed cm7, all my set up was still there. The partion must not have been touched. So don't wait for ics, your stuff is still there. Just get it ack up and running.
I do have one more problem. Preware won't install. Keeps saying system is busy. Anybody get it working or have a way past that?
Edit: and it works now! Server must have been busy.
fyi, on a fresh instll, there are no patch under beta-patches. however, uberkernel, worthog, and F4 are available. and of course govnah is available.
Hmm now to decide if I like WebOS enough to take a chance on losing android or webOS bootlooping.
I had enough trouble getting it all on here the first time around.
So, step 1: remove anything I installed via Preware(everything, just in case)
Step 2: Download webOS 3.0.5
Step 3: Attempt to install
Step 4a: if it installs, done? Or reinstall moboot?
Step 4b: If it fails, run webOS doctor, then install android, cwm, and moboot again after updating to 3.0.5?
That right?
Sent from something with a Ｋモ尺れモㄥ.