If anyone is having issues with Video playback and you haven't updated your radio, go ahead and do so... The new Radio includes updated Video Encoders.
The steps I did (and have no problems with my setup) was:
Full wipe and installed gapps + CM 5.0.7-Test 3
reboot
Then head back into your recovery, clear cache & dalvik-cache
(don't wipe data)
Install Pauls Pre-Rooted-Froyo zip
reboot
I optionally installed the latest .34 BFS kernel from intersectRaven.
Everything is working great for me. No issues with video playback, recording, no market issues, no paid app issues, no radio issues (actually improved dl/ul speed on T-Mobile US)
I recommend everyone try the new radio! If for any reason it doesn't work for you, you can always revert, but it's highly recommend to try it first.
If it's actually the radio that contains the encoders, why go through the hassle of installing CM first if you will overwrite it with Froyo. If it was the radio, straight up flashing the radio img would suffice.
mrandroid said:
If anyone is having issues with Video playback and you haven't updated your radio, go ahead and do so... The new Radio includes updated Video Encoders.
The steps I did (and have no problems with my setup) was:
Full wipe and installed gapps + CM 5.0.7-Test 3
reboot
Then head back into your recovery, clear cache & dalvik-cache
(don't wipe data)
Install Pauls Pre-Rooted-Froyo zip
reboot
I optionally installed the latest .34 BFS kernel from intersectRaven.
Everything is working great for me. No issues with video playback, recording, no market issues, no paid app issues, no radio issues (actually improved dl/ul speed on T-Mobile US)
I recommend everyone try the new radio! If for any reason it doesn't work for you, you can always revert, but it's highly recommend to try it first.
Click to expand...
Click to collapse
Where do we find the latest gapps ?
FaJu said:
If it's actually the radio that contains the encoders, why go through the hassle of installing CM first if you will overwrite it with Froyo. If it was the radio, straight up flashing the radio img would suffice.
Click to expand...
Click to collapse
I was just explaining the steps i took on my setup which is why i don't have any issues...
Try the Pauls update by itself which includes the radio. If it gives you problems, try how I did it.
android.activate said:
Where do we find the latest gapps ?
Click to expand...
Click to collapse
http://www.mediafire.com/file/n02gjyqymj2/gapps-passion-EPE54B-signed.zip
Gapps are in the Froyo.zip from Paul. It is the official release so it comes with the GAPPS. No need to get them otherwise, that will be a different story when it hits AOSP and Cyan puts out a Froyo build.
If anyone is having issues with Video playback and you haven't updated your radio, go ahead and do so... The new Radio includes updated Video Encoders.
The steps I did (and have no problems with my setup) was:
Full wipe and installed gapps + CM 5.0.7-Test 3
reboot
Then head back into your recovery, clear cache & dalvik-cache
(don't wipe data)
Install Pauls Pre-Rooted-Froyo zip
reboot
I optionally installed the latest .34 BFS kernel from intersectRaven.
Everything is working great for me. No issues with video playback, recording, no market issues, no paid app issues, no radio issues (actually improved dl/ul speed on T-Mobile US)
I recommend everyone try the new radio! If for any reason it doesn't work for you, you can always revert, but it's highly recommend to try it first.
Click to expand...
Click to collapse
Interesting
By flashing cyanogenmod first, do you get more choices at locales in froyo? Anyone please confirm this
-------------------------------------
Sent via the XDA Tapatalk App
WebghostDK said:
Interesting
By flashing cyanogenmod first, do you get more choices at locales in froyo? Anyone please confirm this
Click to expand...
Click to collapse
Not 100% sure but I did it so all the apps like superuser and spareparts stay.
/system apps are overwritten when you upgrade from CM to Froyo. There is a superuser app included in Paul's Froyo release, but no "Spare Parts".
maedox said:
/system apps are overwritten when you upgrade from CM to Froyo. There is a superuser app included in Paul's Froyo release, but no "Spare Parts".
Click to expand...
Click to collapse
you're right... either way, i posted that method because it's how I did it and it seems to work good. Others have tried it the way i posted and still no problems... So either it helps or it doesn't, i do it that way cause it works and if it works, why fix it. lol.
upgrading from CM to Froyo is copying files to system and overwrite them if theyalready exists.
BUT
it does not format system, so you keep all your extra-apps
I did the same with Enomther
Any ROM you flash should be formatting the System partition and replacing all existing apps. AFAIK FroYo is the same. They won't wipe the /data partition, and hence your /data/app/ folder will remain intact. If the system is stable with the existing contents of the /data/data/ folder if you don't do a full wipe when cross-flashing, then you're lucky.
/system is formatted as part of the update.zip method - at least with Paul's Froyo release.
I did the same thing, all my paid protected apps are still there and working and I have zero ill effects unlike the first 5 or 6 times I flashed to 2.2 after a full wipe. The phone is blazing fast now, and I kept all of my settings and apps. Win/win.
mrandroid said:
If anyone is having issues with Video playback and you haven't updated your radio, go ahead and do so... The new Radio includes updated Video Encoders.
Click to expand...
Click to collapse
How has it been verified that the new radio includes updated video encoders?
Radio doesnt have any video encoders my brother, video encoders are in the lib folder. Video problem is due to some incompatibilities. Seriously i dont think HTC or Google would be stupid to include encoders in the radio wasting the precious space in the partition
installed froyo.. battery life was terrible.. 12 hours version close to 48.. went back to cyanogen still terrible.. the new radio while giving me a little better performance in my bad coverage area. is constantly trying to get signal and shows using 60% of my cpu/battery.. now reverting back to old radio.
Great dicks on fire, so this is why my video playback has been broken after I ditched Froyo and reverted back to CM. Time to downgrade to older radio with all haste.
charnsingh_online said:
Radio doesnt have any video encoders my brother, video encoders are in the lib folder. Video problem is due to some incompatibilities. Seriously i dont think HTC or Google would be stupid to include encoders in the radio wasting the precious space in the partition
Click to expand...
Click to collapse
Not true. The radio is also the DSP firmware. Those proprietary libs implement the Android HAL and talk to the kernel which offloads all it's media tasks onto the radio.
They've definitely changed the way we talk to the VFE with the FroYo radio, which is why you get a kernel panic when recording video if you use the new radio with 5.0.7.
Also that would be why the custom kernels get the same reaction when installed on Froyo. They don't have some necessary dependencies?
Related
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.)
Hi! I've been using the search feature and How Tos, but my problem is that I just received a warranty replacement Fascinate for my speaker going out, prior to yesterday I was rolling happily along with CommRom UKB, but now with ED05 already on my phone I'm not sure I want to back track... I want to try ccampos784's [ROM][ED05] PowerWashed ED05 ROM and Debloated Touchwiz ED05 ROM, and I have the zip, I understand how to flash that, but don't I need an odin file? And to get CWM or something? Should I use the ones I have from before (cwm-recovery-ALL-3-30-FIX.tar)? and since the Odin file for ED05 is stock, not rooted wouldn't that just be a circle and put me where I am with Stock ED05. My main reason for rooting is Debinging, so... can anyone help me out here please? I think I am just confusing myself more the more I try to research....
download the powerwash ed05.zip and push to your sd
odin cwmall.tar
three finger boot into recovery
wipe data
install zip from sd
Should work fine installing over your current ed05 build...atleast it did for me.
*edit
btw the powerwash ed05 rom is already rooted/debloated/debigned/deodexed/zipaligned/go launcher...etc
Thanks!!!
So Simple and what I've done a bunch of times, I was just making it way more complicated than it needed to be, thanks for the clear "Just do this" Basically. Now I'm embarrassed that I had to ask...
I've rooted and installed roms on other phones before, but this one has me really confused. Currently I've rooted using the ubuntu guide, installed cwm-3-30fix, "modified stock firmware" found in some guide out there that said it was needed to install "latest cwm recovery" which was red 3.xx, curently still on the 2.5cwm 3-30fixall recovery. So should I go back to stock ED04? Update to ED05? Place point me in the direction to install cm7 or other rom. And from what I've read I also need to worry about the modems now? I also tried installing the rom managers recovery, then learned from another thread it doesn't work with the fascinate.
Sent from my SCH-I500 using XDA App
Sorry firmware is 2.2.1 according to my phone. Baseband ed04
Sent from my SCH-I500 using XDA App
Your question cannot be directly answered, but Ill try my best...
-flash the version of cwm that the rom you are trying to install calls for.
-I use cwm 2.5.1.x for all stock rom's and the older froyo roms
-Some newer roms require cwm3
-All mtd roms such as miui, cm7, VGB require cwm4
Read the vanilla gingerbread thread in the development section and that should bring you up to speed. I recommend to odin the verizon official ed05 package in the development section. One reason being you do not need to flash a modified kernal to get cwm to stick. Also the powerwash ed05 package is debinged/ debloated/deodexed/ zip aligned/ rooted. Its a nice functional rom with some tsm enhancements.
Thank you for giving me a place to start! is there info on the modems/radios in the vanilla thread?
Sent from my SCH-I500 using XDA App
MrBlueJK said:
Thank you for giving me a place to start! is there info on the modems/radios in the vanilla thread?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Read this
http://forum.xda-developers.com/showthread.php?t=1013312
There is an app in the market that allows you to make odin backups. Its called odin maker. Haven't tried it yet though. This might be useful at some point in your endeavors.
Sent from my SCH-I500 using XDA Premium App
artvandelay440 said:
There is an app in the market that allows you to make odin backups. Its called odin maker. Haven't tried it yet though. This might be useful at some point in your endeavors.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
Nice! ill have to play around with that...
Thanks Droidstyle! Now I'm on ED05 powerwash. Nice speed compared to stock. I'm very happy now.
Glad to hear you guys are happy with the ROM! Just as a reminder, the PowerWash ROM has been updated since yesterday up to beta v4 and resolves some issues. Check the main thread for more details.
Is anyone else having problems with app storage on the powerwash ROM?
I originally loaded the ROM and after restoring my backups from Titanium the phone became an unusable due to constant crashes of just about everything imaginable. Tried wiping it and restoring a few apps at a time - worked fine until I rebooted at which point all my prefs were gone and the same crashes started before I could even unlock the screen.
So, I decided maybe it was a problem with my backups and decided I'd start clean. I did a full wipe and discovered that I can't install more than about 4 apps before I start getting insufficient space errors. When I go to settings->phone storage, I still have 1.42GB free under internal phone storage.
I've now done the following procedure twice top-to-bottom, and end up with the same results:
- ODIN ED05 OTA ROM & .pit file.
- Boot into ED05
- Setup Google Account
- Load Market -> Install Maps, all 3 Angry Birds variants, Beautiful Widgets, Pocket Cloud (just a few big apps to prove there is no problem with my hardware and that it works under stock).
- Reboot & ODIN CWM.
- Flash PowerWash beta4, wipe davlik, data, cache, battery stats. Confirm voodoo is off.
- Boot into PWb4.
- Setup Google Account
- Load Market -> Install BW, PocketCloud, Maps, Angry Birds. After this, all additional app installs fail due to insufficient space.
A df from the command line shows 1.4GB free on /data and none of the other partitions are 100% full, so I don't think this is a voodoo-partition-with-a-non-voodoo-kernel problem.
As I said, I've done this whole thing twice. Apps install fine on Stock, fail on PowerWash. Nobody else seems to be complaining, so this must be an obvious thing I'm missing, but I'm not sure what. Any help?
OK, this may not be directly ROM related, but I'm not sure how to work around it. From what I can tell, every time I load the market, it must be background updating from 3.0.26 to 3.0.27. If I go into applications, wipe the data and uninstall the update, I can then go into the market and install one additional app. When I try to install another, I'm told there is no space, but if I go to the Applications control panel, I'll see that I've been upgraded to 3.0.27 again. If I uninstall the update and repeat the process, I can get yet another app, but the process keeps repeating itself.
Is there a way to either lock the 3.0.26 market version or to flash back to the old market?
peng1can said:
OK, this may not be directly ROM related, but I'm not sure how to work around it. From what I can tell, every time I load the market, it must be background updating from 3.0.26 to 3.0.27. If I go into applications, wipe the data and uninstall the update, I can then go into the market and install one additional app. When I try to install another, I'm told there is no space, but if I go to the Applications control panel, I'll see that I've been upgraded to 3.0.27 again. If I uninstall the update and repeat the process, I can get yet another app, but the process keeps repeating itself.
Is there a way to either lock the 3.0.26 market version or to flash back to the old market?
Click to expand...
Click to collapse
Want to try this out for me? It flashes back the old market that came with ED05 stock. Flash in CWM, then once you boot up go into settings>applications> Market and clear data and cache on it to clear up any issues.
http://www.mediafire.com/?g7785ds6vdcaoo3
There's another thread (http://forum.xda-developers.com/showthread.php?p=16324333) with another person having the same issue. Seems to be related to the latest market.
I had just finished doing about what you are recommending when you posted.
For reference for anyone else - Once I started searching beyond just the fascinate forums, I've found that 3.0.27 causes problems for a lot of people on other platforms (mostly apps over 30MB will fail, but others at random as well), and there doesn't seem to be a way to block the update from 3.0.26. You have to roll back to the 2.x version (which I did), and that seems to fix the problem.
I'd suggest leaving the 2.x version in the future version of the ROM and making the 3.0 market an addon if people want to experiment with it after google hammers out the bugs.
(Alternatively, people have had luck making a temporary /cache partition inside an ext4 img file, but that seems complicated and hacky to include in a ROM).
Thanks!
peng1can said:
I had just finished doing about what you are recommending when you posted.
For reference for anyone else - Once I started searching beyond just the fascinate forums, I've found that 3.0.27 causes problems for a lot of people on other platforms (mostly apps over 30MB will fail, but others at random as well), and there doesn't seem to be a way to block the update from 3.0.26. You have to roll back to the 2.x version (which I did), and that seems to fix the problem.
I'd suggest leaving the 2.x version in the future version of the ROM and making the 3.0 market an addon if people want to experiment with it after google hammers out the bugs.
(Alternatively, people have had luck making a temporary /cache partition inside an ext4 img file, but that seems complicated and hacky to include in a ROM).
Thanks!
Click to expand...
Click to collapse
Actually, this might be fixed soon, since a voodoo kernel is in the making and it uses Ext4 partitions. Can't give you an ETA (and it's not my kernel), but check the couple last posts in the main ROM thread for details.
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
UPDATED 28.03.12 - CHECK 2nd POST FOR DOWNLOADS!
After flashing latest full version of CM7.2 RC1 by vo-1 [19/3/12] I found that:
* Rom seems to be based upon latest official CM7.2 RC1, if not all at least partially.
* Proximity Sensor works
* Torch works
* Bluetooth works
* Link2sd works
* Includes latest Google Play 3.4.7
* Includes lagloose's GPS/Sensors fix as the gpsd file exists now in system/bin
* Latest Google Maps work, no force closes, very fast
* No lag after disabling live wallpaper and tweak cyanogenmod settings
* Blackhawk OC Kernel included
* Fast rom, no lag
* FOTA KILL which is included in stock roms exists in system/app which didn't by now. Don't know why but I am sure there is a reason
* UPDATE: Battery life is very good. After 2 days of testing I can say that it does nor drain fast.
After that, I think we need the appropriate people to do these:
1. Deodex versions for both full and update rom. Clean versions, no things added or removed. DONE = Check 2nd post
2. FrameworkMod (30 volume steps) for both odex and deodexed DONE = Check 2nd post
3. Pdroid Patch DONE = Check 2nd post
4. I don't know much but I definately know how to prepare ICS Layouts 012 by achep (ready for flash) for deodex version DONE = Check 2nd post
Seems like this rom is reaching everybody's expectations. Please feel free to discuss your experience.
Small issue: Still when opening radio bluetooth activates too. If I recall on nightly that wasn't happening. Correct me If I am wrong
SECTION A - DOWNLOADS FOR 24.4.12 ROM
1. Deodex version prepared by me using xultimate. Link below is the latest full version, not the update from previous versions. Tested and working 100%
DOWNLOAD: Full CM7.2 RC1 by vo-1 24.4.12 DEODEX
2. Deodex version prepared by me using xultimate. Link below is the update from previous versions
DOWNLOAD: Update CM7.2 RC1 by vo-1 24.4.12 DEODEX
SECTION B - DOWNLOADS FOR 26.3.12 ROM
1. Deodex version prepared by me using xultimate. Link below is the latest full version, not the update from previous versions. Tested and working 100%
DOWNLOAD: Full CM7.2 RC1 by vo-1 26.3.12 DEODEX
2. Deodex version prepared by me using xultimate. Link below is the update from previous versions
DOWNLOAD: Update CM7.2 RC1 by vo-1 26.3.12 DEODEX
SECTION C - DOWNLOADS FOR 19.3.12 ROM
1. Deodex version prepared by me using xultimate. Link below is the latest full version, not the update from previous versions. Tested and working 100%
DOWNLOAD: Full CM7.2 RC1 by vo-1 19.3.12 DEODEX
2. Deodex version prepared by me using xultimate. Link below is the update from previous versions
DOWNLOAD: Update CM7.2 RC1 by vo-1 19.3.12 DEODEX
3. FrameworkMod for DEODEX prepared by LPFinch
DOWNLOAD: FrameworkMod vo-1 19.3.12 DEODEX
4. FrameworkMod for ODEX prepared by LPFinch
DOWNLOAD: FrameworkMod vo-1 19.3.12 ODEX
5. FrameworkMod for ORIGINAL prepared by LPFinch
DOWNLOAD: FrameworkMod vo-1 19.3.12 ORIGINAL
6. PDroid Patch prepared by Toxina - DEODEX ONLY (original post here)
DOWNLOAD: PDroid Patch for 19.3.12 CM7.2 RC1 by vo-1 DEODEX
7. Status Bar Now Supports Transparency - DEODEX ONLY. Prepared by me on UOT Kitchen (for transparency to appear you need CM7 Theme Chooser themes that support that) Install guide here
DOWNLOAD: SystemUI.apk
8. ICS Layouts 012 by Achep prepared by me using latest acpatcher5.1 - DEODEX ONLY - DOES NOT SUPPORT STATUS BAR TRANSPARENCY - TO BE USED ONLY WITH SYSTEM DEFAULT SystemUi.apk
Follow instructions or see post41
DOWNLOAD: ICSLayouts v012-patch.zip + ICSLayouts v012-undo.zip
9. ICS Layouts 012 by Achep prepared by me using latest acpatcher5.1 - DEODEX ONLY - SUPPORTS STATUS BAR TRANSPARENCY.
DOWNLOAD: ICSLayouts v012 Trans-patch.zip + ICSLayouts v012 Trans-undo.zip
ATTENTION: First replace your SystemUi.apk with the one I provide above and only that, and then start the procedure for the layouts. Other way round will not work!
10. ICS Theme by Achep modded exclusively for vo-1's rom prepared by me
DETAILS, SCREENS AND DOWNLOAD: Modded ICS Theme exclusively for vo-1's rom
11. Roboto font (all versions) to match ICS Theme and Layouts very brief tutorial by me
INSTRUCTIONS AND DOWNLOAD: Roboto font (all versions)
I'm having lots of problems with Titanium Backup Pro 4.8.4.1, I get FC on scroll, it fails to restore properly. That was an update of 19.03 over 15.03 (clear cache and dalvik), 15.03 was a fresh clean install (format /system and everything else!) which was working OK. Uninstall / reinstall of TB didn't solve it, I wasn't happy to delete my TB backups so reverted to official RC1. It's very rare to get TB problems, which surprised me.
itasoulas said:
After flashing latest full version of CM7.2 RC1 by vo-1 [19/3/12] I found that:
* Rom seems to be based upon latest official CM7.2 RC1, if not all at least partially.
* Proximity Sensor works
* Torch works
* Bluetooth works
* Link2sd works
* Includes latest Google Play 3.4.7
* Includes lagloose's GPS/Sensors fix as the gpsd file exists now in system/bin
* Latest Google Maps work, no force closes, very fast
* No lag after disabling live wallpaper and tweak cyanogenmod settings
* Blackhawk OC Kernel included
* Fast rom, no lag
* FOTA KILL which is included in stock roms exists in system/app which didn't by now. Don't know why but I am sure there is a reason
* Battery life is still under investigation. To be reported soon!
After that, I think we need the appropriate people to do these:
1. Deodex versions for both full and update rom. Clean versions, no things added or removed.
2. FrameworkMod (30 volume steps) for both odex and deodexed
3. Pdroid Patch
4. I don't know much but I definately know how to prepare ICS Layouts by achep (ready for flash) for deodex version
Seems like this rom is reaching everybody's expectations. Please feel free to discuss your experience.
Small issue: Still when opening radio bluetooth activates too. If I recall on nightly that wasn't happening. Correct me If I am wrong
Click to expand...
Click to collapse
Great review man, I agree with all of your observations and about battery, 15/03/12 version was having serious battery draining problems for me, I will be updating this post after a day or so to let you know about 19/03 version.
Cheers...
UPDATE: battery seems to be draining at a similar rate, I changed to smartassv2 and it seems to be a bit better, I used to keep it with performance governor @883Mhz, it had never given such battery draining problem in the past, I will move away from it now.
iandol said:
I'm having lots of problems with Titanium Backup Pro 4.8.4.1, I get FC on scroll, it fails to restore properly. That was an update of 19.03 over 15.03 (clear cache and dalvik), 15.03 was a fresh clean install (format /system and everything else!) which was working OK. Uninstall / reinstall of TB didn't solve it, I wasn't happy to delete my TB backups so reverted to official RC1. It's very rare to get TB problems, which surprised me.
Click to expand...
Click to collapse
Trying now with 4.8.4 Pro version. No FC's while scolling, backing up completed succesfully. I flashed the full version over XWKT7. Don't know why this happened to you and it's really weird problem which I doubt it has to do with rom functionality.
iandol said:
I'm having lots of problems with Titanium Backup Pro 4.8.4.1, I get FC on scroll, it fails to restore properly. That was an update of 19.03 over 15.03 (clear cache and dalvik), 15.03 was a fresh clean install (format /system and everything else!) which was working OK. Uninstall / reinstall of TB didn't solve it, I wasn't happy to delete my TB backups so reverted to official RC1. It's very rare to get TB problems, which surprised me.
Click to expand...
Click to collapse
I didn't experience any problem with TB, I restored my whole 50+ apps with no problems at all in a single batch operation, the only problem I am facing is google Play FCing on me, I will try reflashing gapps and post about results.
Kasnar said:
I didn't experience any problem with TB, I restored my whole 50+ apps with no problems at all in a single batch operation, the only problem I am facing is google Play FCing on me, I will try reflashing gapps and post about results.
Click to expand...
Click to collapse
so far no problems with me with google play. Tried installing some apps, all OK! Maybe the update process from one veriosn to another creates the problem. If possible I suggest testers to try a clean install with the full version over a stock rom.
Kasnar said:
the only problem I am facing is google Play FCing on me
Click to expand...
Click to collapse
Ha, Google Play was working fine for me on 19.03, but was FC going back to my CWM 14.03officialRC1 backup -- my titanium restore on 14.03 of google play from 19.03 fixed the FC...
I manage to make things work with xultimate. Testing now and it's deodexing. Probaby tomorrow late night I'll post the deodex version of 19/3/12
iandol said:
Ha, Google Play was working fine for me on 19.03, but was FC going back to my CWM 14.03officialRC1 backup -- my titanium restore on 14.03 of google play from 19.03 fixed the FC...
Click to expand...
Click to collapse
Flashing latest gapps fixed by FC problem, is all good in the hood, if anyone is interested, i used this to get it fixed:
http://forum.xda-developers.com/showthread.php?t=1536724
Credits to chemicalrage for latest gapps package...
CHECK 2nd Post - Updated with Deodex Version prepared by me (FULL)
Do any of you use Waze? I have never had any problem with it on any rom before, but on this one specifically it closes whenever I try to navigate, I have tried reinstalling, deleting all data, etc, etc and it doesn't work. The app hasn't been upgraded since Feb 23rd so it has to be something with this rom. Just wondering if anyone else is having these kind of issues.
UPDATE: I flashed lagloose's patch and I got a much faster lock, it is included originally but also a bunch of other libs, so on that part at least I got better locks after patching, But waze keeps closing down, it is not a force close, I don't get any kind of pop up, it simply closes abruptly, what a bummer, I use freaking waze everyday, GPS is an important thing to me
Kasnar said:
Do any of you use Waze? I have never had any problem with it on any rom before, but on this one specifically it closes whenever I try to navigate, I have tried reinstalling, deleting all data, etc, etc and it doesn't work. The app hasn't been upgraded since Feb 23rd so it has to be something with this rom. Just wondering if anyone else is having these kind of issues.
UPDATE: I flashed lagloose's patch and I got a much faster lock, it is included originally but also a bunch of other libs, so on that part at least I got better locks after patching, But waze keeps closing down, it is not a force close, I don't get any kind of pop up, it simply closes abruptly, what a bummer, I use freaking waze everyday, GPS is an important thing to me
Click to expand...
Click to collapse
If it was backed up with titanium and restored, uninstall app, reboot phone and clear cache, reboot, restore again with titanium BUT ONLY THE APP NOT IT'S DATA! Other users reported problems with titanium fc but others don't so I guess It has to do with the update prosses of the rom?
I use gps a lot also but can't try that today. But I am sure it's not the rom. Try if possible for you to to a clean install of the full version!
To solve my Titanium Backup problems, I had to delete the persistent settings saved by TB to the /sdcard/ -- so something in the settings setup seemed to trigger this specifically for the 19-03 build.
Check 2nd Post - Updated with update version prepared by me and mediafire links for frameworkmod (odex, deodex, original) prepared by LPFinch
Can we have a more detailed review of this release, please?
I would like to know how performance and battery life compares to stock rom with moderate usage (I don't play games much, but I do browse the internet over Wi-Fi and 3G for 3hr/d). Also, is the phone fully functioning (gps, compass, etc)?
I can't move from stock if i'm losing reliability. Hope someone can report.
shatteringlass said:
Can we have a more detailed review of this release, please?
I would like to know how performance and battery life compares to stock rom with moderate usage (I don't play games much, but I do browse the internet over Wi-Fi and 3G for 3hr/d). Also, is the phone fully functioning (gps, compass, etc)?
I can't move from stock if i'm losing reliability. Hope someone can report.
Click to expand...
Click to collapse
Since this is only 1 day old we don't have sufficient detailed reports. But I don't think anyone here will complain about vo-1's rom. Previous version were great, this one is awesome. But again friend, you have to try things aout by yourself. If everyone were playing safe we wouldn't have such great roms here. The only thing I can say is that the functions you mention work great!
ok, thank you buddy! i'm going straight for a nandroid and a flash...will try and report myself. I was asking because I've flashed much in the past week and really didn't feel like wasting time...I am now on AdrenalineROM and it's good, so I really don't know what to expect more! After all, our phone has its limits.
itasoulas said:
If it was backed up with titanium and restored, uninstall app, reboot phone and clear cache, reboot, restore again with titanium BUT ONLY THE APP NOT IT'S DATA! Other users reported problems with titanium fc but others don't so I guess It has to do with the update prosses of the rom?
I use gps a lot also but can't try that today. But I am sure it's not the rom. Try if possible for you to to a clean install of the full version!
Click to expand...
Click to collapse
I reflashed clean from stock rom, with 3x wipe, deleted waze folder on sd and reinstalled clean from market (not TB restore) and still the problem persisted, I also tried flashing your deodexed version to no avail, I noticed that it also happened to me playing angry birds, I even tried underclocking thinking it could have something to do with high cpu utilization, no fix.
Flashed FAT CM7 clean and no problems whatsoever, I will stick to FAT for the time being, in my opinion both roms are nearly 100% functional with no issues pretty much. Thanks for all the suggestions and good luck
Kasnar said:
I reflashed clean from stock rom, with 3x wipe, deleted waze folder on sd and reinstalled clean from market (not TB restore) and still the problem persisted, I also tried flashing your deodexed version to no avail, I noticed that it also happened to me playing angry birds, I even tried underclocking thinking it could have something to do with high cpu utilization, no fix.
Flashed FAT CM7 clean and no problems whatsoever, I will stick to FAT for the time being, in my opinion both roms are nearly 100% functional with no issues pretty much. Thanks for all the suggestions and good luck
Click to expand...
Click to collapse
Don't know what to say, I installed Angry Birds form Market, played about 5 minutes. No fc, smooth gaming! If you are happy with FAT Rom then I am happy too!!! I haven't found myself any issues, and I don't need to lie about this as I am not getting paid for anything. I am just a great supporter of vo-1's rom
I just tried to flash open gapps 6/4/2020 stock for version 9 arm64, after I wiped cache and dalvik and rebooted all my gapps were gone but google pay was showing. I could see all the others were installed looking in system apps though. Trying to run google pay produced an error, see attached. Play services version seems to be broken? Help?
Confirmed, definitely broken. Logs attached. If anyone finds anyone in the open gapps project that actually cares feel free to let them know but from my past experiences it looks like open gapps stock is now over for 9. Might try a larger package, I'll post here if I do and it solves the problem.
Update: The Super package has the same issue.
There are other GAPPS like Nik GAPPS.
ChazzMatt said:
There are other GAPPS like Nik GAPPS.
Click to expand...
Click to collapse
True, but that's another set of issues, and wouldn't I have to get Open Gapps off first?
callihn said:
True, but that's another set of issues, and wouldn't I have to get Open Gapps off first?
Click to expand...
Click to collapse
Yes, but let's back up a step...
What LOS custom ROM do you have installed, for which you need GAPPS?
Just want to make sure we're all on the same page.
LOS-16 and LOS-17 need different GAPPS and of course stock firmware doesn't use GAPPS.
ChazzMatt said:
Yes, but let's back up a step...
What LOS custom ROM do you have installed, for which you need GAPPS?
Just want to make sure we're all on the same page.
LOS-16 and LOS-17 need different GAPPS and of course stock firmware doesn't use GAPPS.
Click to expand...
Click to collapse
Of course stock uses gapps, unless you like wasting your storage to hold the updates and then having to re-update if you land up having to restore or do a factory reset, been doing it since Gingerbread and it works great, or it did, although the majority of updates can easily be moved to the system using Link2SD I have yet to find any realible means to move play services to the system without breaking things which is a major headache, gapps solves that issue and also allows me to choose which apps I want included in a rooted stock rom. The reality is that custom/non-stock ROMs are generally broken in one way or the other and more often than not it's just not something I'm willing to deal with, in addition there's useally too much junk included that I just have no need for and if I did I'd change my stock rooted ROM to fulfill that need. I've actually never seen a stock ROM that didn't use gapps. I'm perfectly happy with rooted and reasonably de-bloated stock and change things I feel are needed, for example adding in call recording, most custom ROMs would actually leave me doing more work to take things out and put things back in, like why take out the native sms, clock, calculator, calender, keyboard etc. they work, they are free and ad free, they are useally small and thus not really bloat and they are often hard to replace with similar function anywhere near their size.
callihn said:
Of course stock uses gapps, unless you like wasting your storage to hold the updates and then having to re-update if you land up having to restore or do a factory reset, been doing it since Gingerbread and it works great, or it did, although the majority of updates can easily be moved to the system using Link2SD I have yet to find any realible means to move play services to the system without breaking things which is a major headache, gapps solves that issue and also allows me to choose which apps I want included in a rooted stock rom. The reality is that custom/non-stock ROMs are generally broken in one way or the other and more often than not it's just not something I'm willing to deal with, in addition there's useally too much junk included that I just have no need for and if I did I'd change my stock rooted ROM to fulfill that need. I've actually never seen a stock ROM that didn't use gapps. I'm perfectly happy with rooted and reasonably de-bloated stock and change things I feel are needed, for example adding in call recording, most custom ROMs would actually leave me doing more work to take things out and put things back in, like why take out the native sms, clock, calculator, calender, keyboard etc. they work, they are free and ad free, they are useally small and thus not really bloat and they are often hard to replace with similar function anywhere near their size.
Click to expand...
Click to collapse
No, you never flash custom ROM GAPPS on STOCK firmware. It already has built in GAPPS. GAPPS are usually only for LOS/AOSP custom ROM, not even stock based custom ROM. So there's your problem.
If you want to do it, go ahead, but I just know what I've been told by several devs.
When I read your question again, it seemed strange the way the wrote it, so that's why I wanted to clarify.
ChazzMatt said:
No, you never flash custom ROM GAPPS on STOCK firmware. It already has built in GAPPS. GAPPS are usually only for LOS/AOSP custom ROM, not even stock based custom ROM. So there's your problem.
If you want to do it, go ahead, but I just know what I've been told by several devs.
When I read your question again, it seemed strange the way the wrote it, so that's why I wanted to clarify.
Click to expand...
Click to collapse
No my problem is that suddenly play services in Open Gapps does not work, worked fine until this flash. Open Gapps is just Gapps, all versions should be the same as released by Google, as stated I've been doing it since Gingerbread and the only issues it's ever caused is when Open Gapps is broken as mentioned in the first post and photos has also been broken for awhile now as it no longer runs in system/app so I install that from play store and move that myself with Link2SD which puts it in system/priv-app where it works. Not sure which question you are referring to, Open Gapps is broken currently and it's my understanding that all Gapps have to be removed to switch to any other and then there's the learning curve that will come with it. If I had the time I'd just create and maintain a package for just core that wouldn't touch the rest. That will likely become a necessity in the future at the rate things are going. So yes, after all these years I'll continue doing it since it's proven to work, assuming it ever gets fixed though I doubt it will as photos has yet to be fixed and that just requires a change in the install script.
callihn said:
No my problem is that suddenly play services in Open Gapps does not work, worked fine until this flash. Open Gapps is just Gapps, all versions should be the same as released by Google, as stated I've been doing it since Gingerbread and the only issues it's ever caused is when Open Gapps is broken as mentioned in the first post and photos has also been broken for awhile now as it no longer runs in system/app so I install that from play store and move that myself with Link2SD which puts it in system/priv-app where it works. Not sure which question you are referring to, Open Gapps is broken currently and it's my understanding that all Gapps have to be removed to switch to any other and then there's the learning curve that will come with it. If I had the time I'd just create and maintain a package for just core that wouldn't touch the rest. That will likely become a necessity in the future at the rate things are going. So yes, after all these years I'll continue doing it since it's proven to work, assuming it ever gets fixed though I doubt it will as photos has yet to be fixed and that just requires a change in the install script.
Click to expand...
Click to collapse
How long have you owned the V30?
You'll need to factory reset the phone to remove the extraneous GAPPS you installed when stock firmware has GAPPS and different resolution versions of the apps.
You still haven't explained why you need gapps on stock firmware. Every V30 dev who creates a stock firmware ROM says do not install GAPPS.
From Aeron Li, the A.IS. and A.I.X. (stock firmware based ROM) dev, who says NOT to do what you are trying to do:
the bad thing is that he can flash/install mismatched gapps and that may make firmware work wrong, or even make safetynet issues and not working Gapps-related things
Click to expand...
Click to collapse
Boombox dev (another stock ROM) and JohnFawkes one of the devs who create the TWRP flashable zips has said not to flash GAPPS over stock firmware.
You're probably going to cause conflicts. But it's your phone.
ChazzMatt said:
How long have you owned the V30?
You'll need to factory reset the phone to remove the extraneous GAPPS you installed when stock firmware has GAPPS and different resolution versions of the apps.
You still haven't explained why you need gapps on stock firmware. Every V30 dev who creates a stock firmware ROM says do not install GAPPS.
From Aeron Li, the A.IS. and A.I.X. (stock firmware based ROM) dev, who says NOT to do what you are trying to do:
Boombox dev (another stock ROM) and JohnFawkes one of the devs who create the TWRP flashable zips has said not to flash GAPPS over stock firmware.
You're probably going to cause conflicts. But it's your phone.
Click to expand...
Click to collapse
I dunno never had any issues and flashed open gapps a few weeks ago, 20200513 to be exact on this phone, no issues. Actually it was explained in detail. Updates take up space, wiping data removes them and hence bandwidth and time is wasted. Moving updates into system saves space and bandwidth. Again I don't do anyone's ROMs I use stock and make the few changes I desire. The only real issue that requires it is moving play services to the system since everything else is movable using Link2SD.