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
Is super user 3.0 not responsive? mine is sometime trouble and laggy, force close SU and/or wipe data needed, to make it work again, how about you? and how to make it works flawlesly?
Same issue. I uninstalled the update because it was too temperamental. Now works fine again. I think its because of my custom kernel.
Sent from my X10i using XDA App
works fine with me....stock kernel with Nocturnal rom
i dont remember with rom i tried but at least 3 roms have this problem
I have same problem but fixed when i cleared the logs and then clear the data from application>manage application>su select clear data.
I did updated the App from the market, and after that, i did the update inside the SuperUser APP.
No problems found until now.
Hi
I flashed my Galaxy S II with AOKP Milestone and Dorimanx V 5.92 and I am getting random reboots. I have never seen my phone reboot, but every once in a while I have to enter the pin to the SIM-card
From what I read Kernel and Rom should be stable, but what can I do? It never booted while in use, only when it was in my pocket.
Should I change Kernel? But which one? Dorimanx seams to be very strong for JB.
leo
Random reboots are 99% application related.
Have you installed any particular app lately?
Have you tried clearing cache, Dalvik cache and fix permissions?
I only re-installed two applications WhatsApp and WeatherPro from many that were running fine before.
On flashing I did clean dalvik an cache.
Fixing permissions? Where should I start?
"Fix Permissions" is an option in CWM. I think it's in the advanced section of CWM
You could also try SD Maid to clean up the phone, and CacheCleaner-NG to clean cache from all your apps, so you don't have to it one by one.
Also, did you have the random reboots before migrating to AOKP and Dorimanx?
You don't use the good kernel, you have to use the 7.8 version
Sent from my GT-I9100 using xda premium
Ok, I fixed permissions, cleaned with SD Maid, cleaned Cache with ChacheCleaner-NG
I had no reboot issues before moving to Dorimanx and AOKP.
Regarding Kernel Version: I used ICS + JB no Mali Kernel V 5.92
should I use the JB Mali Kernel?
If you use JB rom then you must use the 7.8 version which is the last one
Sent from my GT-I9100 using xda premium
ok, I will do change that
Thanks
The reboots have improved, however they have not disappeared completely.
I deinstalled all applications except WhatsApp to make sure that the reboots are not caused by any applications.
What I have noticed ist that my battery status indicates that the phone is charging even though that is not the case!
How can I solve this problem? I really like AOKP!
I never have this issue but have a look here :http://forum.xda-developers.com/showthread.php?t=1664893 maybe that can help you
Hi, I would like to tell you my series of unfortunate events.
I was on Stock Android Rom with my International s3.
Yesterday i got bored and i installed Revolution Hd Rom (32). It was awesome! i liked 4.2 and i liked that it was stable/fast.
My main concern WAS the stability and speed about roms. And Revolution was flawless.
So while i was setting up my phone, i did something HORRIBLE!
I was trying to install Jobnik's slow mo camera app with cwm. But stupidly i tried to flash it like a rom (Used app to reboot and install rom.)
So my device was stuck on boot. (on samsung logo)
- I tried to wipe cache
- Tried to wipe cache + dalvik cache
- Tried to wipe cache + dalvik cache + factory data reset+user data wipe (a little problem there though, all of my files were still there.)
And nothing helped.
I give up.
I was lucky, i had the rom image on my sd card root. So i flashed it again. Installed with aroma. And ta-dah! My phone was back!
SOO here comes my problem;
- Now my rom is so slow! I have some flickering issues too. When i first installed i've selected some tweaks. (build.prop, sqlite and seeder.)
Second time i didn't.
Now i don't want to flash my rom AGAIN
Is there any way for me to get those tweaks again. OR even is that possible those tweaks were THAT important.
My phone feels like **** now. Please point me towards somewhere.
I've installed Watchdog and there are no apps that hogs my cpu. So i think my performance issue lies somewhere else.
- Note: My account is new, so i couldn't posted to the rom's thread. (Also couldn't able to find an Official Q&A thread.)
Thanks in advance.
UPDATE
I was poking around and i found out if i disable HW Overlay from Developer options flickering issue goes away and it "seems" like i have less lag.
But what i've read about this option tells me to not disable it because HW overlay is good for performance & battery. Should i disable it. Or does my ROM requires HW to be disableD?
Would post this question in the relevant development thread but I don't have enough posts yet.
I'm using the Infamous PAC rom compiled by kasper_h in this thread.
My problem is with the Paranoid Android "hybrid settings" included with the rom. In the UI settings I can set the interface mode to be exactly how I like (tablet UI, 140 dpi, etc.). After changing a setting and pressing Save, the system UI will restart immediately and correctly display the updates I've made. However, after a restart of the tablet it reverts back to 360p phone UI mode. As far as I can tell my color changes have held (statusbar and navbar are transparent as I wanted).
Has anybody run into a similar issue with a Paranoid ROM or have some tips to get these settings to persist after reboot? Thanks.
Edit: It is worth mentioning that I've installed Apex launcher in place of the default Trebuchet, but I've tried booting with and without the "use tablet UI" checked, and neither prevents the system UI from reverting.
JeSuisNerd said:
Would post this question in the relevant development thread but I don't have enough posts yet.
I'm using the Infamous PAC rom compiled by kasper_h in this thread.
My problem is with the Paranoid Android "hybrid settings" included with the rom. In the UI settings I can set the interface mode to be exactly how I like (tablet UI, 140 dpi, etc.). After changing a setting and pressing Save, the system UI will restart immediately and correctly display the updates I've made. However, after a restart of the tablet it reverts back to 360p phone UI mode. As far as I can tell my color changes have held (statusbar and navbar are transparent as I wanted).
Has anybody run into a similar issue with a Paranoid ROM or have some tips to get these settings to persist after reboot? Thanks.
Edit: It is worth mentioning that I've installed Apex launcher in place of the default Trebuchet, but I've tried booting with and without the "use tablet UI" checked, and neither prevents the system UI from reverting.
Click to expand...
Click to collapse
Thats a stable rom… but. I had problems with it also. Some devices just dont like certain roms.
You might try a clean flash… .wipe data, cache, dalvik. And format system. Yes this can make a difference.
Short of that… you could try a different kernel. And see if that helps. I always thought that was the issue on my device… as his kernels always cause me some kind of issue i have to fix. But ive yet to have the problem your having.
Gil81 said:
Thats a stable rom… but. I had problems with it also. Some devices just dont like certain roms.
You might try a clean flash… .wipe data, cache, dalvik. And format system. Yes this can make a difference.
Short of that… you could try a different kernel. And see if that helps. I always thought that was the issue on my device… as his kernels always cause me some kind of issue i have to fix. But ive yet to have the problem your having.
Click to expand...
Click to collapse
Hmm, that seems to have done it. I hadn't run across isntructions that suggested formatting /system, but after a clean install plus that my issue seems to be resolved, as well as some annoying homescreen jumping around. Thanks!