yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] triplex76:
if you open the last v11 you can see how sensor.default.so is already inside the package

I suggest to always look inside zip files you download... at least you know what are you going to overwrite inside your tab and so if you want to go back before pushing just make a copy of what is going to be overwrited...make sense? I'm just tired ... sorry
[Galaxy Tab  Android Development] Peter Unger:
...and any update any ZIP also.
[Galaxy Tab  Android Development] celestar32:
There is no point flashing this kernel as the SD card doesn't mount and recognise in the tab.
[Galaxy Tab  Android Development] triplex76:
as already discussed it's not a general issue...it happens depending by the rom you got.
[Galaxy Tab  Android Development] shmigao:
Edit 3: successfully restored from CWM backup, but cannot access internal SD (unmounted)... well what to do now?
[Galaxy Tab  Android Development] Peter Unger:
Hmmm - reading all these messages and making some experiments with version 11 maybe the CWM implementation is the issue?

After installing MoDaCo with MoDaCo kernel, CWM works fine, i can install e.g. Gen X theme with CWM.

After installing v11 kernel, installing a theme with CWM did not work, backup & recovery also does not work.

Installing the v11 did not install the sensors drivers too. I ha to do this manually.

Could all this trouble be caused by some broken CWM implementation?

If i talk nonsense: Forgive me - still learning all this stuff :o
[Galaxy Tab  Android Development] shmigao:
yes, that is true

but the thread title says:

"MCR EXT4 compatible"

however several people that have this ROM report problems, with no boot, and no sd card access
[Galaxy Tab  Android Development] TheGrammarFreak:
No.

I just flashed using the PDA option through ODIN.

EDIT:

Wiped my internal SD card too. Bye bye nandroid backup :(

EDIT:

I don't mind btw, I just thought you should know.
[Galaxy Tab  Android Development] richardtrip:
ext4? I need to know what the problem was so maybe we can fix (or warn).
[Galaxy Tab  Android Development] TheGrammarFreak:
Nah, I was on RFS using Roto's JME V4
[Galaxy Tab  Android Development] rmanaudio:
OK found 1 problem:

This kernal does not work well with the sensors on my Rogers/AT&T tab. The Tab will not flip screens. Gyro sensor not working and in calibration screen the ball does not move.
[Galaxy Tab  Android Development] GANJDROID:
Richard is working on the Tab too?! Wahoooooooo :D

Sent from my GT-P1000
[Galaxy Tab  Android Development] richardtrip:
Very weird because i'm using Roto's JME V4 myself and it didn't wipe anything on my sd (internal and external). Ddi you use odin without anything selected?
[Galaxy Tab  Android Development] jamesbond007uk:
Install on Roto JME4

Hello,

Is this safe to flash with ODIN 1.7 on ROTO JME4 full flash image?

Flash the kernel file as PDA, right?

Good work!

Thx

Tom
[Galaxy Tab  Android Development] TheGrammarFreak:
Not sure, I just started ODIN and use the PDA option to flash the kernel. I'm gonna restore (somehow) and then try though Heimdall ;)
[Galaxy Tab  Android Development] richardtrip:
Compiling a usagsm version right now.
[Galaxy Tab  Android Development] rmanaudio:
You are the best
[Galaxy Tab  Android Development] jamesbond007uk:
Pls let me know if Heimdall works...

No REPARTITION, right?

Thx.

Tom
[Galaxy Tab  Android Development] jongilluley:
Odin by default does a repartition if you don't deselect it so this would be why yours was wiped.
[Galaxy Tab  Android Development] TheGrammarFreak:
I wasn't replying to you, sorry

I hate ODIN
[Galaxy Tab  Android Development] richardtrip:
Can you try this one:

http://xda.richardtrip.org/tab/GalaxyTab_1200_uvoc_usagsm_V1.tar

If it is ok please report back.
[Galaxy Tab  Android Development] rmanaudio:
No go...just gives me a blank screen. It is working in the back ground...but no picture!

Flashed back to V1 Euro and picture again.
[Galaxy Tab  Android Development] b0ricuaguerrero:
just used pda and flashed without repartition being checked, also get distortion when it reboots. im not the only one that having the issue.
[Galaxy Tab  Android Development] richardtrip:
Not so easy to debug without your device :-(

gonna check it later but thanks for testing (if i have anything new to test i'll let you know).
[Galaxy Tab  Android Development] rmanaudio:
I figure...maybe Roto can help better...he has the same model.
[Galaxy Tab  Android Development] lexi1986:
Hey Richardtrip,

Same problem here, flashed it with Odin and my tab has been "Wiped" don't flashed it with repartition "checked" for me no problem that it's wiped, can i help you with something like output from my phone or something ? I got a Dutch Galaxy TAB with JME Roto V4
[Galaxy Tab  Android Development] richardtrip:
that was about something else actually :-)
[Galaxy Tab  Android Development] kay_kiat88:
+1. had to do a full flash to get everything back. different people have different results. no idea why but im on v10 for now. perhaps maybe it's the different tabs that give different results? i have asian tab and v11 causes the same issues that you've posted above. doesnt boot.. after restoring sdcards wont mount etcetc..
[Galaxy Tab  Android Development] shmigao:
OK. i am probably now there, where you were.... i reflashed modaco's r3 kernel, but still have the sdcard not mounted problems...

so how did you flash back?

modaco r1 wipe zip in CWM recovery, or how did you come back to a full working tab?
[Galaxy Tab  Android Development] shmigao:
no, it's not Asian vs. Euro, because I have a EURO tab, and MCR EXT4 (= all the prerequisites mentioned in the thread title/OP), but still it didn't work.

I also didn't have any other kernel before, i straight went from Roto's JMG to Modaco Kernel r3, with conversion to EXT4, and then to Modaco ROM r1
[Galaxy Tab  Android Development] Peter Unger:
Did you try to start with Roto JMI, then ModaCo Kernel r3 and then ModaCo ROM and finally flash the new kernel?

This was my upgrade path and everything was OK except CWM now (and you have to update manually the sensors driver).
[Galaxy Tab  Android Development] shmigao:
i once (weeks ago) upgraded from Roto JMG to Modaco r3 and then Modaco ROM

we have almost exactly the same path, except for JMI vs. JMG, which i really cannot see being the reason for this, as Modaco r1 ROM is also JMI based
[Galaxy Tab  Android Development] spandsbab:
Tried this kernel as well and now I can't mount /sdcard... any advice what to do next?
[Galaxy Tab  Android Development] kay_kiat88:
I did a full flash using Odin to get my tab running again.

Here's what I did to get my tab running again-

Since v11 didn't work, I did a full flash with partition to rotojmiv2. Then I flashed the modaco r3 kernel. Restored my backup from yesterday which is modaco rom. Then I flashed v10.

Here's what I tried previously -

When my tab did not boot up, I did a full flash to rotojmiv2. Then I flashed r3 modaco kernel. Installed modaco rom full wipe. And flashed v11 still couldn't boot up. So I gave up v11 and did what I wrote above to get my tab running again.
[Galaxy Tab  Android Development] antiochasylum:
Has anyone wiped the caches before flashing? I did and everything works perfect. I'm on a US att tab with jj4 bootloaders.

I know in the HTC world wiping caches usually clears alot of things up.
[Galaxy Tab  Android Development] spandsbab:
I tried this one before flashing the kernel but actually out of habit only as I think this practice is just for when flashing new ROMs... I'm on Euro Tab P1000...:(
[Galaxy Tab  Android Development] kay_kiat88:
And did it work? I'm guessing no cos of your :( lol.
[Galaxy Tab  Android Development] shmigao:
i did wipe cache too ... unfortunately that didn't do the trick either

btw... this reminds me that wiping Dalvik-Cache on CWM recovery still doesn't work...
[Galaxy Tab  Android Development] kay_kiat88:
guess we'll just have to wait for v12:D?
[Galaxy Tab  Android Development] Peter Unger:
On v10 or v11? On v10 it works for me, v11 seems not to work.
[Galaxy Tab  Android Development] Guitarfreak26:
So has no one managed to save the tab without a full reparation? That's a bummer... we need rich to post lol
[Galaxy Tab  Android Development] spandsbab:
Actually I will be trying your method now...:)
[Galaxy Tab  Android Development] kay_kiat88:
Okay.. good luck. My method didn't work for me. Make sure you backup everything!
[Galaxy Tab  Android Development] Bigmille:
Hi everybody,

I flashed the V11 zImage using Heimdall but the tab is stuck on the Samsung logo (the white logo with flashing blue glow). I've tried to factory reset the tab in recovery mod but it can't mount sd card.

I've also tried V10 with Hemdall flash but the device gets stuck on the 1st logo in boot up.

I reseted the tab to factory condition and formatted the internal sd card before flashing, and my tab is an unlocked euro model.

Can somebody please show me how to return the tab to the stock kernel? Right now the tab is just an expensive paper weight.:(

Thanks
[Galaxy Tab  Android Development] instechgainza:
Few pages back, we experienced the same thing, some of them did restore back up to get their tab in life, but if there is no option to restore then odin is your friend, simply flash full rom with a pit partition and it all back to work.
[Galaxy Tab  Android Development] jeebspawnshop:
Do NOT flash this kernel with that firmware. I did it, and after a few hours of trying everything to rescue it and get it all working properly (see sdcard mounting issues), I had to full reflash / repartition in Odin.

Wait until this is fixed to work with more ROMs than just Modaco and Overcome.

I'm hoping it all gets fixed soon, cuz this kernel is dynamite!
[Galaxy Tab  Android Development] Guitarfreak26:
Think its worth me holding fire incase theres a simple solution to fix? I dont wanna wipe again :( lol
[Galaxy Tab  Android Development] Bigmille:
Thanks for the quick reply, I only backed up my apps and system files, not the original kernel, do you know where or how I can get a pit file?
[Galaxy Tab  Android Development] kay_kiat88:
Version 10 is actually okay. Just that the gyro when in gallery and nfs is broken.
[Galaxy Tab  Android Development] Guitarfreak26:
I really dont wanna lose everything, ill curse if i wipe then theres a simple fix lol..

Damn me for being so eager for voodoo sound..
[Galaxy Tab  Android Development] Guitarfreak26:
Some of us are having issues with Modaco mate.. I dunno whats causing it..
[Galaxy Tab  Android Development] captain134:
I installed v11 from CWM. I was already on v10 and I use MCR. I wiped cache partition before install. Everything works great except for the sensors. They do not work at all now. I will try to push the file to it when I get a chance then it should be 100% and very fast/stable. Thanks again for the great work!

BTW my quadrant score is 2238 now and I got a 19.46 mflops on linpack.
[Galaxy Tab  Android Development] Guitarfreak26:
I really dont get the problem..

I was on modaco R1, had v10 previous and just flashed update.zip. I didnt wipe the cache though. Only got a doorstop atm lol
[Galaxy Tab  Android Development] antiochasylum:
So am I the only person that everything works so far?? Wow I feel special and even leaving my tab @1.4 the temp never went above 86 degrees
[Galaxy Tab  Android Development] Peter Unger:
No - here it works too. But CWM does not work correctly, mounts the internal SD instead of the external one. No backup/restore or update is working except flashing back to v10.
[Galaxy Tab  Android Development] captain134:
Can someone please post the commands to push the sensors file through adb shell? I have searched but cant seem to find them now. Thanks in advance.
[Galaxy Tab  Android Development] antiochasylum:
Adb remount

Adb push sensors.default.so /system/lib/hw

Adb reboot

Sent from my MoDaCo powered Galaxy Tab.
[Galaxy Tab  Android Development] captain134:
are you trying to install through CWM? The way I do it is I downloaded the V11.zip, moved the file to my ext sd, boot into recovery, select install update.zip not apply update.zip, then select .zip file from ext sd not apply update.zip, press yes install and it should work.

Sorry if I am stating the obvious. I am just confused @ why your "flashing" update.zip not GalaxyTab_1400_MCR_ext_V11.zip
[Galaxy Tab  Android Development] Guitarfreak26:
Yeah it was my wording mate. i flashed the proper file.. select zip etc...
[Galaxy Tab  Android Development] Bigmille:
Hi, does anyone know if this is the righ firmware version for UK unlocked Tab?

P1000XWJJ7

Many thanks.
[Galaxy Tab  Android Development] ronjon31:
Worked beautifully on my Bell Tab, wiped cache and installed with CWM.

Quadrant scores over 2200

EDIT: Spoke to soon, had to push sensors.default.so but that was simple enough. Everythjing is working fine now.
[Galaxy Tab  Android Development] captain134:
I just pushed the v10 sensors file to the device and now everything is working (even NFS) 100% Thanks again for all the hard work.

This is on a Bell tab with Modaco
[Galaxy Tab  Android Development] Basil 123:
I used the root explorer app to copy the file sensors.default.so from sdcard then pasted it over the faulty one in system\lib\hw. Rebooted and all is well with the sensors...

adb was reporting that the file was read only and wouldnt let me push it...

Nice kernel - will have to play a bit with it and see how it goes...

Cheers

Basil
[Galaxy Tab  Android Development] antiochasylum:
Back on V10 with clockwork not mounting external SD for backup and restore I don't like. Sensors don't work either however even after pushing the file. Oh well ill deal with it.

Sent from my MoDaCo powered Galaxy Tab.
[Galaxy Tab  Android Development] Guitarfreak26:
Did you do a full wipe mate or just flash the zimage?
[Galaxy Tab  Android Development] richardtrip:
Ok,

fresh start from Update1. ondemand governor working fine now so i think that was the problem with the previous builds. Maybe some people are using setcpu and set the governor to ondemand or interactive. It's was ok when already booted, but not on boot (but fixed now :-).

Expect an update real soon (as in minutes).
[Galaxy Tab  Android Development] Guitarfreak26:
Thanks Rich, Will i have to do a full wipe to get this all working again?
[Galaxy Tab  Android Development] richardtrip:
Update:

Version 12:

*Ondemand governor default

*cfs scheduler now default

*Added interactive governor

*sensors file to previous version

download: http://xda.richardtrip.org/tab/GalaxyTab_1400_MCR_ext_V12.zip

flash with recovery (or extract the file and flash the zImage from the kernel directory)
[Galaxy Tab  Android Development] bendjlee:
Hi Trip, would your latest update be safe to run on overcome 1.1.3?

Or are there limitations i the kernel that makes it only work on Modaco r1...

Cheers
[Galaxy Tab  Android Development] richardtrip:
Extract the kernel and flash with heimdall. btw did you use setcpu to set the governor to ondemand or interactive on boot? if so im pretty sure you have no problem with this kernel.
[Galaxy Tab  Android Development] richardtrip:
Overcome is using the MCR kernel or isn't that the case atm?
[Galaxy Tab  Android Development] bendjlee:
Yes, v11 was not compatible hence I ask. Anyhow I try once my nand restore completes
[Galaxy Tab  Android Development] memmerson:
Hi richardtrip, i've been using ginger villain on my Desire since its initial release and I love it. Wondering if you have any plans for a build for the Tab?
[Galaxy Tab  Android Development] Peter Unger:
Short question @richardtrip:

On v10 i get a short colour flickering after the initial boot screen.

On v11 this was missing and looked like original ROM.

On v12 it is flickering again.

Is there the possibility to get rid of this flickering?

BTW: CWM works again on v12, perfect :)

...thank you for all your effort! :)
[Galaxy Tab  Android Development] bendjlee:
V12 working on overcome rom . Trmperture sensor non responsive. (Flashed via cwm - so sensors should have been picked up)

Caution to those wanting to overclock this kernel on overcome

Cheers
[Galaxy Tab  Android Development] wallah:
+1 Yeah thats very nice !!! :-D
[Galaxy Tab  Android Development] TheGrammarFreak:
V12 sensors are screwed (NFS is screwed) Also, the interactive governor just locked to 100MHz (It did for me at least)
[Galaxy Tab  Android Development] Guitarfreak26:
Still stuck on samsung bootlogo. i put .tar at the end of zimage and flashed it..

i didnt have setcpu installed all i had used was voltage control..

:(

EDIT - + SDCard still not mounting in CWM
[Galaxy Tab  Android Development] Peter Unger:
Works perfect here - did you recalibrate?
[Galaxy Tab  Android Development] Guitarfreak26:
Im thinking i should wipe and install..
[Galaxy Tab  Android Development] TheGrammarFreak:
Ye. Car just locks hard left :(
[Galaxy Tab  Android Development] wallah:
Wipe dalvik cache, flash v12 kernel via recovery and no probleme here for the moment on Overcom 1.1.3....

Thanks a lot Richardtrip !!!!!

edit: temperature sensor not working, bloqued at 30%
[Galaxy Tab  Android Development] jkurl:
I am also on overcome 1.1.3 and I have had no problems. I just ran quadrant and got 2459. Awesome job Richard.
[Galaxy Tab  Android Development] bendjlee:
Does your temperature sensor fluctuate? or is it a constant 30degreees / 86 fareniheit ?

Additionally i am curious to find out if you are able to steer correctly in a game such as nfs shift

I am wondering if i am missing something...

Cheers
[Galaxy Tab  Android Development] Peter Unger:
Hmmm - if you recalibrate and you turn the tab like you would within NFS, does the ball follow the same angle right and left or does it show the same behaviour like in NFS?

BTW: I tested only at 1,2 GHz...now on 1,4GHz - no problem...
[Galaxy Tab  Android Development] Basil 123:
Was working fine, but latest sensor file has games stuck on left tilt. Tried to paste the last sensors.default.so but now root explorer cant change the file from read-only.

Sure itll get sorted out really soon. Thanks for the update :-)
[Galaxy Tab  Android Development] Guitarfreak26:
Went to rotos... then converted with mck.. then installed modaco rom... now its booted... Thankgod for that.. god knows why it didnt earlier...
[Galaxy Tab  Android Development] antiochasylum:
Clockwork works for me now too, however the sensors still don't. Even again after pushing the new file. Shrug oh well.

Thanks richard for your work.
[Galaxy Tab  Android Development] Peter Unger:
So i am really the only one being happy with CWM, sensory, etc.? Can´t believe it...will wait for my second Tab coming back from Samsung and hope to have no issues there too.
[Galaxy Tab  Android Development] retroqwe:
i am unable to get the v11 release to work using overcome 1.1.3 tried twice
[Galaxy Tab  Android Development] TheGrammarFreak:
Mine stays at that temp. Quite disconcerting

Calibrate tool shows the expected behaviour

Lucky sod.
[Galaxy Tab  Android Development] Basil 123:
Strange. I flashed back to v11, rebooted,sensors still stuck. Then flashed v12, wiped cache/dalvik-cache and they worked!

All fine now. Enjoying the kernel, thank you :-)
[Galaxy Tab  Android Development] retroqwe:
ok just seen v12 is now out [topic still says v11] will try that
[Galaxy Tab  Android Development] Guitarfreak26:
Yeah i noticed tab is running hot but im on 1.4 and installing lots of apps

Cant fault rich for this though, voodoo sound and the speed increase is amazing!
[Galaxy Tab  Android Development] TheGrammarFreak:
I'll try wiping some caches then...
[Galaxy Tab  Android Development] vinclar:
Recommended UV are: 50 50 150 75 75 100

I put this, am I right?

-50 for 1.4Ghz

-50 for 1.2Ghz

-150 for 1Ghz

-75 for 800Mhz

-75 for 400Mhz

-100 for 200Mhz

-100 for 100Mhz

Im asking it because I have 7 paths for change and only six recomendations I maintain the same voltage for 100Mhz and 200Mhz , any expirience lowering more the voltage?

Thanks in advance.
[Galaxy Tab  Android Development] instechgainza:
calibrated the sensor and try to test nfs shift and much better then before now it goes straight without steer left & right control..lol
[Galaxy Tab  Android Development] Guitarfreak26:
Weird error here... i applied the generation x blue theme and ive got a plane over my signal bars its not connecting.. i tried putting flight mode on but it dont work properly..

is that a kernel bug? lol
[Galaxy Tab  Android Development] bendjlee:
go into phone settings and check if your baseband is "unknown" ive seen this happen before when flashing different kernels. you may need to reflash your modem here.

I would like to know if anyone running the overcome rom has a working temperature sensor? if you see a static 30degrees / 86 Fahrenheit that does not count!, i know this cos my phone should never be at this temp even when it boots up it should be around 33-35 (i expect to see my phone go anywhere from 28-41 degrees based on usage)
[Galaxy Tab  Android Development] Guitarfreak26:
Yes mate your right.. it says unknown... what one do i flash for modaco euro tab?

Heres me thinking the modem was included lol
[Galaxy Tab  Android Development] bendjlee:
I am using the modem bundled with roto's v5 rom - try that one
[Galaxy Tab  Android Development] Guitarfreak26:
v5? I can only see jmi v2 lol
[Galaxy Tab  Android Development] bendjlee:
sorry, my mistake - there is only one modem so you can't go wrong anyhow 8-)
[Galaxy Tab  Android Development] crisvillani:
Its seems temp. Sensors arent working stays stuck at 30 degrees.
[Galaxy Tab  Android Development] jkurl:
Mine is the same w/ the temp. Stuck as 30°.
[Galaxy Tab  Android Development] natious:
my temp is working, says 32*, has gone up to 35* while charging my phone (via setcpu widget)
[Galaxy Tab  Android Development] jkurl:
I am using the same widget. What rom are you using. I am using the overcome rom.
[Galaxy Tab  Android Development] bendjlee:
based of your sig, you are running Modaco R1 correct?

As it appears temps don't work under overcome 1.1.3 at this point. (i could be wrong, but its not working for me)
[Galaxy Tab  Android Development] jkurl:
Bend I think you are right. I am running the overcome rom and they are not working.
[Galaxy Tab  Android Development] crisvillani:
No im running Modaco and it doesnt work for me also nfs doesnt work either.

Sent from Overclocked Galaxy Tab.
[Galaxy Tab  Android Development] natious:
You need to replace the senosors.so file with the one from the first page, then your sensors will work
[Galaxy Tab  Android Development] crisvillani:
Did that already battery sensors still.doesnt work , sensors work, but playing games that use accelometer dont work.
[Galaxy Tab  Android Development] bendjlee:
Cool this is the sorta "promising" response i was hoping for, i will try later (fingers crossed)
[Galaxy Tab  Android Development] natious:
did you reboot the tab after you replaced the file, if you used root explorer to replace it, did you fix the file permissions?
[Galaxy Tab  Android Development] jkurl:
I did mine via root explorer but it didn't fix anything. i rebooted and it is still the same when you talk about permissions does that need to be fixed in the sensor file or another file.
[Galaxy Tab  Android Development] crisvillani:
Ya fixed permissions and then rebooted. Hopefully Richard can find a fix for this.
[Galaxy Tab  Android Development] jkurl:
what about pulling the sensor file from the other OC thread or did you use that one cris?
[Galaxy Tab  Android Development] crisvillani:
Ya tried that one and the on the first page, does someone have V11update .zip i want to try the sensor.so file in there.
[Galaxy Tab  Android Development] jkurl:
cris here it is.

here is all his versions. http://xda.richardtrip.org/tab/
[Galaxy Tab  Android Development] crisvillani:
Thnks : )

Sent from Overclocked Galaxy Tab.
[Galaxy Tab  Android Development] jkurl:
i just tried the v11 sensors, reset permissions and rebooted. it is still a no go. stuck at 30 degrees.
[Galaxy Tab  Android Development] crisvillani:
Ya same but now accelometer in games works for me!