Related
Hiya everyone,
I've ported Dumfuq's overclocking patches from 2.6.29 to 2.6.32.21! This applies to those of us using the stock HTC OTA and allows the use of programs like SetCPU. This kernel was built from the source code from http://developer.htc.com and the kernel config is an identical copy of the one included in the latest Froyo OTA (my leak).
My current method of providing this is as an update.zip... just put this on your SDcard, boot into Clockwork, and flash it. If it kills your kittens, do not blame me.
Also, reminder: flashing this zip alone is not enough to overclock your device. Afterward, use a program (from the Market) such as SetCPU to overclock your device.
Download: http://www.multiupload.com/2XEWYRL62U
Change Log:
- Revision 2
Fix Wifi issues (as well as any other kernel module loading issues).
Add support for CPUfreq governers 'interactive' and 'smartass'.
Change the default governer from 'ondemand' to 'interactive' - this dramatically improves redraw performance and other user-interface responsiveness.
To change to the Smartass governer use something like SetCPU.
Include the MSM KGSL TLB performance tweak changes that are present in CM's kernel repository. You may or may not notice any video performance improvement, but it provides a possibility of improvement.
Fixed the kernel version string to properly read '2.6.32.21' not '2.6.32.17' - the first version wasn't .17, it was .21.
Please remember to disable the HTC Perflock in SetCPU by pressing the Menu key (while in SetCPU) and selecting 'Perflock Disabler'.
Happy? Donate.
Hey I'm running your NB 2.15 Mod ROM and just flashed this kernel. It broke the WiFi. I am now getting an Error when attempting to enable WiFi.
What is the max frequency of this kernel? And does it include smartass governer?
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
pettigrew95 said:
Hey I'm running your NB 2.15 Mod ROM and just flashed this kernel. It broke the WiFi. I am now getting an Error when attempting to enable WiFi.
Click to expand...
Click to collapse
Ahh, one thing I didn't test, although I suspected it might break. I'll fix it tonight and post a new update.zip for ya'll.
agentg1001 said:
What is the max frequency of this kernel? And does it include smartass governer?
Click to expand...
Click to collapse
It's identical to Dumfuq's patches, so 864000Hz. And no, it doesn't include the smartass governer - I will investigate that possibility tonight, however I suspect I will be able to implement it. Additionally I will be disabling HTC Perflock in the kernel so it doesn't have to be done by SetCPU.
Toodles.
EDIT: I'll also be adding the new 'interactive' CPUfreq governer.
nbetcher said:
Ahh, one thing I didn't test, although I suspected it might break. I'll fix it tonight and post a new update.zip for ya'll.
It's identical to Dumfuq's patches, so 864000Hz. And no, it doesn't include the smartass governer - I will investigate that possibility tonight, however I suspect I will be able to implement it. Additionally I will be disabling HTC Perflock in the kernel so it doesn't have to be done by SetCPU.
Toodles.
EDIT: I'll also be adding the new 'interactive' CPUfreq governer.
Click to expand...
Click to collapse
I have made the changes, however I decided to NOT disable HTC Perflock through the kernel config, so please make sure to disable it (via SetCPU) first before trying to overclock or change your governer. New version uploaded, see OP.
Could you also include some higher frequencies? (Preferibly up to 960)? That would be great because my phone is stable up to 921. Also compcache enabled (like drowning child's kernel) would be awesome.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
I'm not sure why but my slide didn't like this kernel
http://pastebin.com/hVgG467j
Thank the devs for nandroid!
My slide not working with this kernel too (
Are you both running NB_Mod-2.15.531.1 Revision 2? Otherwise this won't work properly. Besides, according to that logcat your problems aren't related to the kernel... Android is unable to mount any of the MTD partitions (/system, /cache, /data, etc).
Please let me know more about what you're running.
Also, I'll be working on making a separate version of this that has OC enabled up to 960MHz, but 960MHz is very dangerous... 800MHz+ is even asking for trouble despite our processor's normal clockrate being 800MHz (T-Mobile downclocked it to 600MHz out-of-the-box).
I'll look into Compcache as well.
im IN.
good job, will try after work. gj
how long does it take to boot the first time?
been stuck at the white MT3GS boot screen for a few minutes now.
running CM7 RC4
EDIT: oops, did not know this is only for the leaked froyo update
pettigrew95 said:
Hey I'm running your NB 2.15 Mod ROM and just flashed this kernel. It broke the WiFi. I am now getting an Error when attempting to enable WiFi.
Click to expand...
Click to collapse
I just flash the this new Kernel and i'm also getting Error on the WiFi when trying to Enable it, also the SetCPU won't go higher then 600. The Rom i'm using is the 3rdSense 1.00
Thankfully i did a Rom Backup so i'm restoring my system
Sefy said:
I just flash the this new Kernel and i'm also getting Error on the WiFi when trying to Enable it, also the SetCPU won't go higher then 600. The Rom i'm using is the 3rdSense 1.00
Thankfully i did a Rom Backup so i'm restoring my system
Click to expand...
Click to collapse
This kernel is only to be flashed if youre running NB Mod 2.15 ROM. It wont work on 3rd sense
pettigrew95 said:
This kernel is only to be flashed if youre running NB Mod 2.15 ROM. It wont work on 3rd sense
Click to expand...
Click to collapse
Well, it showed it as the kernel in the "About" so it appeared to have flashed it (and it did kill the WiFi) so it did get flashed
Either way, i got back to the previous one (.17[aka .21]) and it's working fine again.
Sefy said:
Well, it showed it as the kernel in the "About" so it appeared to have flashed it (and it did kill the WiFi) so it did get flashed
Either way, i got back to the previous one (.17[aka .21]) and it's working fine again.
Click to expand...
Click to collapse
Hmm, .17 isn't AKA .21. They're two different kernels and contain different code. The kernel you're using in 3rdSense was from the HTC Legend release of 2.6.32.17 and had different Wifi drivers. When a kernel and its driver modules are built, the build process puts the kernel's version string into the modules, so if you try to load them on a different kernel it will fail. This is what happened to you... you have 3rdSense which uses 2.6.32.17 Wifi drivers and my 2.6.32.21 kernel cannot (well, I fib a little on that) load the .17 drivers. Get it? Got it? Good.
nbetcher said:
Hmm, .17 isn't AKA .21. They're two different kernels and contain different code. The kernel you're using in 3rdSense was from the HTC Legend release of 2.6.32.17 and had different Wifi drivers. When a kernel and its driver modules are built, the build process puts the kernel's version string into the modules, so if you try to load them on a different kernel it will fail. This is what happened to you... you have 3rdSense which uses 2.6.32.17 Wifi drivers and my 2.6.32.21 kernel cannot (well, I fib a little on that) load the .17 drivers. Get it? Got it? Good.
Click to expand...
Click to collapse
So... what you are saying is, a kernel from a different device all together, is working on a hardware which it doesn't really belong to. While a Kernel made specifically for this, will kill the WiFi of the device it's designed for?
From what i recall from Linux, and i could be wrong and this doesn't apply to Android, the Kernel and the UI are two separate components. The Kernel has all the drivers and the UI is the interface! but again, i could be wrong.
Sefy said:
So... what you are saying is, a kernel from a different device all together, is working on a hardware which it doesn't really belong to. While a Kernel made specifically for this, will kill the WiFi of the device it's designed for?
From what i recall from Linux, and i could be wrong and this doesn't apply to Android, the Kernel and the UI are two separate components. The Kernel has all the drivers and the UI is the interface! but again, i could be wrong.
Click to expand...
Click to collapse
What I'm saying is that the boot.img that I have in the update.zip from this post does NOT contain the modules for Wifi since the modules are stored on your /system MTD and the scope of this update.zip is for the kernel. Could I replace the modules from there with the ones shipped with the Froyo OTA? Sure, but where does it stop?
Anyways, the Legend is not a completely different device. The Legend is basically the UK version of the Slide, minus the keyboard. Same exact hardware all the way down to the Wifi and BT.
Let me explain things a little bit more:
There's sdio.ko and tiwlan_drv.ko in /system/lib/modules. NB_Mod has ones compiled from 2.6.32.21, 3rdSense has ones compiled from 2.6.32.17. This thread's kernel (boot.img, to dumb it down a bit ) is 2.6.32.21. So, when the system goes to load the modules from /system/lib/modules, it sees that you're running kernel 2.6.32.21, but the modules in that directory are for 2.6.32.17. It fails.
As far as Android being separate from the kernel... yes, of course. But touching "Wifi" (to enable Wifi) in Settings doesn't scurry out little Android gremlins to magically carry the firmware from your MTD to the Wifi chipset... all it does it say "Hey, kernel, would you mind loading the wifi module you have listed in init.rc? Thanks Linus! *kisses*" Then Android does some other stuff, but I won't bore you with the entire process or else I'll have to write a book (oops, too late).
EDIT: in hind-sight this all seems to not really answer your question and only further supports the need for a better answer to you, but hopefully you'll find some clarity.
nbetcher said:
What I'm saying is that the boot.img that I have in the update.zip from this post does NOT contain the modules for Wifi since the modules are stored on your /system MTD and the scope of this update.zip is for the kernel. Could I replace the modules from there with the ones shipped with the Froyo OTA? Sure, but where does it stop?
Anyways, the Legend is not a completely different device. The Legend is basically the UK version of the Slide, minus the keyboard. Same exact hardware all the way down to the Wifi and BT.
Let me explain things a little bit more:
There's sdio.ko and tiwlan_drv.ko in /system/lib/modules. NB_Mod has ones compiled from 2.6.32.21, 3rdSense has ones compiled from 2.6.32.17. This thread's kernel (boot.img, to dumb it down a bit ) is 2.6.32.21. So, when the system goes to load the modules from /system/lib/modules, it sees that you're running kernel 2.6.32.21, but the modules in that directory are for 2.6.32.17. It fails.
As far as Android being separate from the kernel... yes, of course. But touching "Wifi" (to enable Wifi) in Settings doesn't scurry out little Android gremlins to magically carry the firmware from your MTD to the Wifi chipset... all it does it say "Hey, kernel, would you mind loading the wifi module you have listed in init.rc? Thanks Linus! *kisses*" Then Android does some other stuff, but I won't bore you with the entire process or else I'll have to write a book (oops, too late).
Click to expand...
Click to collapse
Everyday you learn something new! thanks for being the teacher!
nbetcher said:
Are you both running NB_Mod-2.15.531.1 Revision 2? Otherwise this won't work properly.
Click to expand...
Click to collapse
Well now I feel a bit sheepish, I guess that's what I get for not reading closely enough, I'm running CM7 RC4, sorry about that.
Does anyone happen to have a copy of this kernel laying around somewhere? Megaupload is long gone unfortunately
I have been having numerous issues trying to get ICScrewd to run on my phone and I am almost certain its a kernel issue.
It was suggested that I swap out the kernel before flashing and that sounds like a great idea to me.
Except...... I don't know how.
Is it as simple as taking the zImage from the kernel zip I want and placing it in the rom zip I want?
Can I ignore the META-INF folder or do I need to somehow merge that over too?
I am sure there is a wiki or a how-to on this but I have looked and cant find it. Its probably because I don't know phrase my search.
But anyway, if someone could point me in the right direction I would be very grateful.
FireRaider said:
.
Is it as simple as taking the zImage from the kernel zip I want and placing it in the rom zip I want?
Click to expand...
Click to collapse
Yup it is that simple, just replace the file with the one you want.
You can also clean up with kernel cleaning script then flash entropy kernel in recovery
Sent from my SGH-I777 using Tapatalk
yoderk said:
Yup it is that simple, just replace the file with the one you want.
Click to expand...
Click to collapse
Working on it now. Thanks.
jivy26 said:
You can also clean up with kernel cleaning script then flash entropy kernel in recovery
Sent from my SGH-I777 using Tapatalk
Click to expand...
Click to collapse
My poor phone locks up even in recovery running Siyah. Its crazy.
I am going to try this like you suggested in your thread.
I should be reporting back soon.
It worked!
So far, so good.
I havent had a single locked up screen or SOD since I flashed.
Thanks guys!
Interesting, i've been using siyah for a long time and never experienced any issues.
Sent from my GT-I9100 using Tapatalk
im running icscrewed with siyah and its working just fine
Just curious since I have never tried a mod with any major changes, what are the benifits of changing out the Kernel, and what are the differences between them?
crimsonconcepts said:
Just curious since I have never tried a mod with any major changes, what are the benifits of changing out the Kernel, and what are the differences between them?
Click to expand...
Click to collapse
For myself the benefit was actually being able to run the ICScrewd rom at all.
In my experience of several years of flashing, some kernels just wont work with some phones.
It sound odd and all that, but my real world experience has led me to give each kernel I am interested in several tried and if they continually crash my phone I move on. I have no idea why this would be. Coming from the Captivate I tried all sorts of kernel and rom combinations. If they didn't work well I just moved on.
As far as different kernels go, some have better battery life than others due to built in tuning I believe. They can be cleaned up to help your phone run faster. And obviously from my experience here in this thread, help your phone be stable.
Excuse my noobness, please. I figured this would be a pretty relevant thread to post this question.
I flashed Siyah 2.6.9 via Odin and then in recovery installed ICScreweD. Did doing so revert my kernel to the older version of Siyah used in the rom?
If so, can I just flash in the newer version using Odin or should I research another method?
This is my first root/mod so I'm still a little nervous about messing up.
Kasdarack said:
Excuse my noobness, please. I figured this would be a pretty relevant thread to post this question.
I flashed Siyah 2.6.9 via Odin and then in recovery installed ICScreweD. Did doing so revert my kernel to the older version of Siyah used in the rom?
If so, can I just flash in the newer version using Odin or should I research another method?
This is my first root/mod so I'm still a little nervous about messing up.
Click to expand...
Click to collapse
yes this reverted to the older kernel included in the rom, to flash the newest kernel. Load the zip of the kernl onto your sd card, enter CWM and flash the zip. Much easier to do than with odin.
Thanks! I was pretty sure that was the case but figured I should ask anyway. I've been lurking these forums for a while and it's awesome how helpful this community is to everyone.
While on the subject of ICScreweD, is there anything I will lose by going to the green edition? The website is kinda unclear as to if there are any features not yet available in the green edition.
Kasdarack said:
Thanks! I was pretty sure that was the case but figured I should ask anyway. I've been lurking these forums for a while and it's awesome how helpful this community is to everyone.
While on the subject of ICScreweD, is there anything I will lose by going to the green edition? The website is kinda unclear as to if there are any features not yet available in the green edition.
Click to expand...
Click to collapse
This is the list of things that differ from the Blue edition which is 2.0.1 and the green edition which is still 1.6.2. Quiet a few differences and it is more up to date.
Version 2.0.1 (Changes since 2.0 are blue) (Full Wipe Required) BLUE EDITION ONLY AT THIS MOMENT
Updated to XWKL1 (Much smoother and improved battery life. Also resolves WiFi issues.)
Siyah v2.6.7
Added Roboto Font
Updated to Jkay v13.4.1
Added LiveWallpapers Support back
ICS & GB Ringtones, Alarms, and Notifications
ICS Boot Animation much sharper and true black
Bluetooth On icon enabled
Removed screenstate scalling
Removed Fancy Rotations (It will be added to the add-ons section)
CPU Governor set to OnDemand
Double Setup is fixed. It was being caused by GoLauncher. So setup will not be prompted when phone first boots. You will see the normal homescreen then about 20 secs later it will appear.
Added CWM Manager v3.0 by Chainfire
Removed MiLocker (You can grab it from the market if you want to continue using)
Phone APK
- Rethemed it slightly again.
Camera APK themed thanks to ssconceptz Click here to show him love
Google Music moved to Data/App/ (So you can remove it and add any music app if you do not want to use it.)
GTalk issues fixed.
Updated Following Apps
BLN Control v1.3.8
File Manager v1.12.4
GO Launcher EX v2.76
Kies Air v2.1.112201
Maps v6.1.1
Voice Search v2.1.4YouTube v2.3.4
yoderk said:
This is the list of things that differ from the Blue edition which is 2.0.1 and the green edition which is still 1.6.2. Quiet a few differences and it is more up to date.
Version 2.0.1 (Changes since 2.0 are blue) (Full Wipe Required) BLUE EDITION ONLY AT THIS MOMENT
Updated to XWKL1 (Much smoother and improved battery life. Also resolves WiFi issues.)
Siyah v2.6.7
Added Roboto Font
Updated to Jkay v13.4.1
Added LiveWallpapers Support back
ICS & GB Ringtones, Alarms, and Notifications
ICS Boot Animation much sharper and true black
Bluetooth On icon enabled
Removed screenstate scalling
Removed Fancy Rotations (It will be added to the add-ons section)
CPU Governor set to OnDemand
Double Setup is fixed. It was being caused by GoLauncher. So setup will not be prompted when phone first boots. You will see the normal homescreen then about 20 secs later it will appear.
Added CWM Manager v3.0 by Chainfire
Removed MiLocker (You can grab it from the market if you want to continue using)
Phone APK
- Rethemed it slightly again.
Camera APK themed thanks to ssconceptz Click here to show him love
Google Music moved to Data/App/ (So you can remove it and add any music app if you do not want to use it.)
GTalk issues fixed.
Updated Following Apps
BLN Control v1.3.8
File Manager v1.12.4
GO Launcher EX v2.76
Kies Air v2.1.112201
Maps v6.1.1
Voice Search v2.1.4YouTube v2.3.4
Click to expand...
Click to collapse
Green is upto date thought I removed the blue only thing
Sent from my SGH-I777 using Tapatalk
UPDATED: added version 1.14 to this post (and pushed it to Play Store as well)
please let me know if it works good (doesn't reboot) when applying settings on stock rooted kernel.
Hi!
I'm trying to make my app TouchScreenTune to work on default kernel on ATT version of Galaxy Note. But since I don't have it myself (I have European Note), I obviously need some feedback from people with I717
This is for GingerBread kernel (however in the case on N7000 it works on ICS as well)
Could you please check if ToouchScreenTune test version attached to this post works with your rooted kernel? Especially I'm interested if it works with stock kernel. Just try to adjust SPen position to some extreme offset - you will immediately see it when pressing screen with SPen.
Thanks.
P.S. Description of the app from the Market after the break
----------
Market link: https://play.google.com/store/apps/details?id=com.vital.tst.n7000&hl=en
*Requires Root*
*Currently supports Samsung Galaxy Note (tested on N7000), Galaxy S2*
*THIS IS TRIAL VERSION!!! FULL VERSION REQUIRES REGISTRATION AND IS PAID*
NorthAmerican/AT&T Note users - see comment regarding kernel below!!!!
TouchScreenTune application allows you to fine-tune settings of phone's touchscreen and calibrate Pen cursor position for every screen orientation (portrait/landscape...). (S-pen calibration obviously works only for Note)
It allows to dramatically improve responsiveness and sensitivity of touchscreen.
If you are using screen protector on your phone, the application will allow to raise screen sensitivity, so there will be no responsiveness impact from using screen protector.
This application allows you to calibrate amount of touch movement, when actual reporting of scrolling starts. That allows more smooth feeling of the interaction with the touch screen.
Without this application you cannot precisely draw or click small items with Pen because it reports position incorrectly - few millimeters away from the actual touch point. But this application allows you to precisely calibrate position of Pen touch on the screen. (Galaxy Note only)
Some common problems:
When first starting there should be popup from SuperUser application with request to get Root access. Some people say that sometimes it doesn't appear. In that case try starting the SU program first, and then this application.
This application supports standard Samsung firmwares - with custom kernels it may not work (however I have successfully tested it with some custom kernels)
Custom kernels: app requires kernel with KALLSYMS, so ask developer of your kernel to include this in his config when building kernel: CONFIG_KALLSYMS=y, CONFIG_KALLSYMS_ALL=y
Known issues: if when first starting application it seems to be not responding, and dialog asking to force close app comes - choose wait. This should happen only on first run.
Hi- I read sonewhere TST does not work with the stock att kernel. You need to root and flash a kernel that supports it from the development section.
Sent from my SAMSUNG-SGH-I717 using xda premium
I have the paid version and run rooted with custom kernel and can't get it to work
Sent from my note running a jelly bean key lime pie hybrid OS
It does not appear to change anything. I set the x and y offsets to 300 each and the target did not change position relative to the pen placement.
bendotson said:
Hi- I read sonewhere TST does not work with the stock att kernel. You need to root and flash a kernel that supports it from the development section.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
That's why I'm posting this test version here - I want to make it work
I have compiled it to work with kernel sources that were published by Samsung.
lactardjosh said:
It does not appear to change anything. I set the x and y offsets to 300 each and the target did not change position relative to the pen placement.
Click to expand...
Click to collapse
That is with stock kernel? Are you rooted? Have you seen any error message when you changed values and hit Apply?
vitalij said:
That is with stock kernel? Are you rooted? Have you seen any error message when you changed values and hit Apply?
Click to expand...
Click to collapse
My apologies...I should have been more specific about my set up.
I'm using a custom ROM based off the leaked ICS 4.0.3 firmware. I'm rooted with SuperSU, but the kernel is stock since we don't have source for the ICS kernel yet.
I do get an error message
ERROR: Can't read SPEN settings? No ROOT Permissions? Unsupported firmware?
Click to expand...
Click to collapse
Is this for GB or ICS?
lactardjosh said:
My apologies...I should have been more specific about my set up.
I'm using a custom ROM based off the leaked ICS 4.0.3 firmware. I'm rooted with SuperSU, but the kernel is stock since we don't have source for the ICS kernel yet.
I do get an error message
Is this for GB or ICS?
Click to expand...
Click to collapse
This is compiled for GB, however in the case of N7000 it works on leaked version of ICS as well. However judging from your error - either ICS leak lacks Kallsyms support or driver is much changed compared to GB version.
I have also uploaded one more test version - which possibly may work better.
vitalij said:
This is compiled for GB, however in the case of N7000 it works on leaked version of ICS as well. However judging from your error - either ICS leak lacks Kallsyms support or driver is much changed compared to GB version.
I have also uploaded one more test version - which possibly may work better.
Click to expand...
Click to collapse
Parsing error when trying to install the new version.
Stock GB kernel does not have KALLSYMS. It was added for some custom kernels, though.
My guess is that ICS does not have this either.
lactardjosh said:
Parsing error when trying to install the new version.
Stock GB kernel does not have KALLSYMS. It was added for some custom kernels, though.
My guess is that ICS does not have this either.
Click to expand...
Click to collapse
Uploaded new version again - now it seems to be OK.
Regarding Kallsyms - stock actually should have it - at least according to kernel sources published by Samsung, and also some people reports. So it would be really nice if somebody with stock kernel could test it.
vitalij said:
Uploaded new version again - now it seems to be OK.
Regarding Kallsyms - stock actually should have it - at least according to kernel sources published by Samsung, and also some people reports. So it would be really nice if somebody with stock kernel could test it.
Click to expand...
Click to collapse
Same error with 1.13 on ICS
ERROR: Can't read SPEN settings? No ROOT Permissions? Unsupported firmware?
Click to expand...
Click to collapse
I bought the app from you off the market.
It did work on the holo kernel.
However, on Seraphim ICS build it doesn't.
I actually uninstalled the program.
The spen is off by 1 square in s-memo. Not too bad.
ICS is much better about the sensitivity and tracking
I had them set to 0 and 25 as recommended but like I said that was too much so I just uninstalled.
does not work on un-rooted, stock att ...
Good to see you hear, i loved using this on GB.
Running ICS from the collective, it loads up but won't apply any requested changes.
May have to wait till the kernel is released and KALLSYMS is added in.
Hi vitalij,
I am running a rooted but otherwise totally stock at&t galaxy note. I tested the application but couldn't notice a difference with the spen settings, even moving them to the extremes.
I tested the application in the marketplace as well. It would open and let me adjust the settings (again, didn't notice a difference) but when I applied the changes my device would reset. I upgraded to the full version and the same thing happened. When I redownloaded the test version the reboot fixed itself, but the settings still don't make a difference on the pen.
Hope this helps!
Sent from my SAMSUNG-SGH-I717 using xda premium
I tested your second version and is working...what i did Ok from what I'm seeing I uninstalled super su and installed superuser in market,,the newest update allowed a superuser prompt..which I allowed.(.I hit back and the setting don't stick,if I hit home they do when I ..and go back in the values stick))..and is super responsive holy sh!t...I can't even type its so fast..lmao..gotta work with these settings.,am running gb unofficial rom on da_gv2 overclock kernel,...dev you have something good going here ...good luck with progress this app will be incredible
Captured screenshot..wont allow me to post...with su command..damn..
Su
Thanks Wish! Backing out with the home button instead of the back button fixed the app for me. Awesome app vitalij!
Sent from my SAMSUNG-SGH-I717 using xda premium
Are you on GB or ics?
Hi there, guys!
I have a problem with Quickoffice. When It tries to open an xls file I get FCs all the time...
This did not happen in the past with version 2.3.5.
I am currently on system version 672.180.33.XT910.Retail.en.EU (build number 6.7.2-180_SPU-19-TA-11.2 - Android 4.0.4)which was flashed with rsdlite after a full wipe on the phone. The phone is also rooted, and that's it. I haven't deleted any bloatware...
Does anyone else experience a similar issue with quickoffice? Any ideas about what should I try to do in order to fix this?
P.S.: Since I installed this version I keep wondering why I did it and did not stick with the good old 2.3.5 version. I am also having issues with other things, e.g. smart actions is not working correctly sometimes - the rules are not being correctly applied, but this is minor...
ChriZathens said:
Hi there, guys!
I have a problem with Quickoffice. When It tries to open an xls file I get FCs all the time...
This did not happen in the past with version 2.3.5.
I am currently on system version 672.180.33.XT910.Retail.en.EU (build number 2.7.2-180_SPU-19-TA-11.2 - Android 4.0.4)which was flashed with rsdlite after a full wipe on the phone. The phone is also rooted, and that's it. I haven't deleted any bloatware...
Does anyone else experience a similar issue with quickoffice? Any ideas about what should I try to do in order to fix this?
P.S.: Since I installed this version I keep wondering why I did it and did not stick with the good old 2.3.5 version. I am also having issues with other things, e.g. smart actions is not working correctly sometimes - the rules are not being correctly applied, but this is minor...
Click to expand...
Click to collapse
Try to disable "Force GPU rendering"
YES!!!! I could never think that something like that could be caused by GPU rendering
I can't thank you enough my friend!!!
Thanks a million! I wish I could hit thanks more times, lolll
ChriZathens said:
YES!!!! I could never think that something like that could be caused by GPU rendering
I can't thank you enough my friend!!!
Thanks a million! I wish I could hit thanks more times, lolll
Click to expand...
Click to collapse
I'm glad it worked. You're welcome.
Hey guys, my question is essentially what the title says. I find that in CM10 based roms, that whenever I use the stock cyanogen mod browser, it automatically goes into desktop mode (and is stuck there. The desktop mode checkbox, however, is unchecked.) I'm fairly sure it worked before I used the touch pad fix here - http://forum.xda-developers.com/showthread.php?t=1893343 - So I think it might be a framework/build.prop issue, but I'm not sure. I've been looking to fix this problem everywhere but haven't really been able to find a solution. Do you guys have any idea what the fix might be?
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
smokerman said:
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
Click to expand...
Click to collapse
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
fishvtt said:
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
Click to expand...
Click to collapse
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Hey, smokerman, would you know how to mess with .jar files. I kinda want to go exploring to see if I can do anything.
you have here a simple guide by @CriGiu
http://forum.xda-developers.com/showthread.php?t=2322231
could help you.:good:
fishvtt said:
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
Click to expand...
Click to collapse
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
Oh ok, I'll try testing that out.
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
All right, well that seems to do the trick. When I try to use the touchpad activator app, it gives me the "error 5 expected reciever of type android.view.ViewRoot, but got android.view.ViewRootImpl". But, Dead Trigger works perfectly how it's supposed to, and the stock browser is using the mobile version now. Just remember to make the necessary build.prop changes as outlined in Fahrenheit's guide.