Related
You read the title correctly.
HDMwIn now supports HDMI out on gingersense. Congrats to TeamWin for this fine release. I have been waiting for HDMI out support for a while.
agrabren said:
The Alpha kernel is now available from Kernel Manager! Give it a test drive!
(Sense only)
We'll be porting the whole re-architecture over to CM7. Not gonna leave AOSP out to dry!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=17068475&postcount=1850
This new kernel is a complete rewrite of the app. The functionality is now fully automatic and no longer requires a separate app. The team has said they do plan on releasing an App to allow those who wish to tinker with settings to do so, but otherwise, a seperate app is unneeded. Gone are the daemon downloader loops.
More indepth information is available here:
http://www.androidcentral.com/android-central-exclusive-hdmwin-gingerbread-first-look
How long did it take you to perfect HDMwIn for Gingerbread?
I've spent over 100 hours getting all the little details right and all the algorithms working smoothly. I anticipate another 10-20 hours until all the wrinkles are fixed.
So HDMI just outputs on its own? The user doesn't need to do anything?
Exactly. The user plugs in the HDMI cable, and it just works. The user is welcome to make adjustments via the UI, but there's generally no need. But there will always be someone who is fussy and wants it to lock rotation, change scaling or modify the overscan defaults.
Did there not used to be auto-rotation? And does auto-rotation work for everything? I noticed it worked in both Nova and the YouTube app.
There was a rudimentary version of auto-rotation in old builds, but that required the UI to read the sensors. This consumed massive amounts of battery, and performed poorly. This new method requires no extra power, and offers a smoother experience to the user. Any application which natively handles rotation (either fixed, like Nova, or dynamic, like Messages) will work out-of-the-box. As for YouTube, YouTube isn't mirroring. It uses native HDMI support for Gallery videos and YouTube videos. That was one of the great new features. You no longer need to disable mirroring to use YouTube. It switches automatically.
You mentioned there's now YouTube app support. Is there also support for videos played in the browser app?
Only the YouTube app and Gallery app support HDMI out-of-the-box from HTC. So when those apps run, you'll have different output on your TV from your device. If you're playing video (or anything else) on the device in a player which doesn't natively handle the EVO's HDMI port, you'll get full mirroring. If the app is HDMI-aware, you'll get the app's intended behavior.
Are there any performance enhancements in the new HDMwIn? How are the scrolling speeds compared to the previous version?
We're using the same "Silky Johnson" technology which drove our previous accelerated kernels, so we're seeing the same smooth responsiveness and performance. Because we now do aspect scaling a little more accurately, it's possible the GPU isn't quite as taxed as before, but we haven't felt a noticeable difference. The device no longer has a polling loop running in the background, so that helps battery life and performance as well.
You mentioned there's a custom kernel involved. What kind of features does this kernal support? Are other kernals supported?
I always build our new features directly on top of the HTC kernels. Once we release the kernel and source code, we work with other kernel developers to get our code integrated into their kernels. This kernel has all the latest EDID fixes (for people who would plug in a TV and have the phone immediately crash) as well as the HDMI mirroring.
Click to expand...
Click to collapse
Video Preview available here:
http://www.youtube.com/watch?v=gu7OVC31Nc4&feature=player_embedded
Warning!!
The kernel has been released on Kernel Manager. This is a free app available on Android Market. Before installing this kernel, please nandroid your phone. This is an alpha kernel. There may be instabilities and other issues. Be aware that installing this kernel will override any other custom/stock kernel you may have installed. You will lose the abilities of those kernels (such as overclocking, HAVs, etc.). This requires root. Do NOT use this kernel with an ASOP rom (MIUI, CM7, etc.). An ASOP version is coming according to the devs.
How to install:
Apparently, kernel manager has issues with the HDMwIn kernel, so please flash from recovery manually instead.
- Run Kernel Manager and approve the superuser request.
- Press menu and select 'Advanced Options'. Ensure 'Flash automatically' isn't checked.
- Select Load Kernel List.
- Scroll to the bottom of the list.
- Select PoonSense 2.3.3.
- Press Download + Flash Kernel.
- Using a file manager, navigate to root of SD card. sdcard/kernel-manager/agrabren contains a .zip file callled "2.3.3-1-793-HDMwIn-Sense233-Alpha-signed.zip". That file is also attached to this thread.
- Move that .zip file to the root of your SD
- Reboot into recovery
- Wipe cache and dalvik cache.
- Flash the .zip file.
- Reboot
- Enjoy HDMwIn.
Also, agrabren has updated his kernel due users having issues with blank screens. If you guys are having issues, please use his newest kernel: build 793. That version is now available on Kernel Manager and attached to this thread.
http://forum.xda-developers.com/showpost.php?p=17074174&postcount=1864
Old method of install. Causes Wifi errors and other bugs, use alternative method above.
Code:
[B]How to install:[/B]
- Install Kernel Manager from Market
- Run Kernel Manager and approve the superuser request.
- Press menu and select 'Advanced Options'. Ensure 'Clear Cache' and 'Clear Dalvik Cache' are checked.
- Select Load Kernel List.
- Scroll to the bottom of the list.
- Select PoonSense 2.3.3.
- Press Download+ Flash Kernel.
- After the reboot, enjoy HDMI mirroring. There is no app to start or configure. It just works now. Plug in an HDMI cable and you are good to go.
Excellent! Can't wait to try... of course I just lost my HDMI cable
deleted post I was in the wrong forum.
Is this kernel godmode compliant?
Sent from my PC36100 using Tapatalk
Hi Guys,
I have a simple question, Is this kernel compatible with the Stock Ver on Gingerbread ?
Also is this kernel support Wireless N ?
Thanks
Khilbron said:
Is this kernel godmode compliant?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Since I didn't hear an answer on this, I downloaded the kernel from Kernel Manager (poonsense 2.3.3) made a backup of Synergy RC2+Godmode. Flash was sucessful, ROM booted with no problems. When I get home in 4 hours I will hook up my HDMI cable and test functionality.
Is anybody having WIFI problems after flashing? I flashed last night, this morning I get "Error" under Settings -> Wireless & Networks -> WiFi (the word Error is right below the word Wi-Fi; attempting to click the checkbox does nothing. It stays unchecked).
Might be a coincidence, as I was also updating my GPS driver last night as well.
mpsantiago said:
Is anybody having WIFI problems after flashing? I flashed last night, this morning I get "Error" under Settings -> Wireless & Networks -> WiFi (the word Error is right below the word Wi-Fi; attempting to click the checkbox does nothing. It stays unchecked).
Might be a coincidence, as I was also updating my GPS driver last night as well.
Click to expand...
Click to collapse
I can confirm this I didn't think to test my WiFi after flashing. I receive the error message as well.
Sent from my PC36100 using Tapatalk
mpsantiago said:
Is anybody having WIFI problems after flashing? I flashed last night, this morning I get "Error" under Settings -> Wireless & Networks -> WiFi (the word Error is right below the word Wi-Fi; attempting to click the checkbox does nothing. It stays unchecked).
Might be a coincidence, as I was also updating my GPS driver last night as well.
Click to expand...
Click to collapse
This will happen if you flash the new kernel through kernel manager. All you have to do is flash the kernel manually and everything *should* work fine.
Go into recovery, clear cache and delvik. Then go to flash file from sd, scroll to the folder called kernel manager, then open the agrabren folder and there will be the flashable zip. Note, this only works if you have already downloaded the file through kernel manager. Otherwise you will have to find the zip file in the dev area. I will include a link soon to the zip.
Find the link here... Second post down (I think)...
http://forum.xda-developers.com/showthread.php?t=987592&page=188
P.S. Always Nandroid Backup prior to any flashing... I am no pro, this is simply the method that worked for me.
I hope this helps, it worked for me the exact same way on all 3 of my EVO's.
Thanks to agrabren and all who contributed, this is one amazing piece of work!! Everything works flawless!
Sent from my S-OFF OG EVO using XDA Premium App
ABBUB said:
This will happen if you flash the new kernel through kernel manager. All you have to do is flash the kernel manually and everything *should* work fine.
Go into recovery, clear cache and delvik. Then go to flash file from sd, scroll to the folder called kernel manager, then open the agrabren folder and there will be the flashable zip. Note, this only works if you have already downloaded the file through kernel manager. Otherwise you will have to find the zip file in the dev area. I will include a link soon to the zip.
Find the link here... Second post down (I think)...
http://forum.xda-developers.com/showthread.php?t=987592&page=188
P.S. Always Nandroid Backup prior to any flashing... I am no pro, this is simply the method that worked for me.
I hope this helps, it worked for me the exact same way on all 3 of my EVO's.
Thanks to agrabren and all who contributed, this is one amazing piece of work!! Everything works flawless!
Sent from my S-OFF OG EVO using XDA Premium App
Click to expand...
Click to collapse
I didnt use Kernel Manager to flash it, I downloaded the kernel, booted to Ra Recovery, backed up my current ROM, then wiped Cache 3x, and Dalvik 3x, then i manually flashed the zip via install zip from SD Card, and my WiFi still errors out. So what you said is irrelevant to the issue. I appreciate your attempt to try and fix it, but the fix is not a fix.
Khilbron said:
I didnt use Kernel Manager to flash it, I downloaded the kernel, booted to Ra Recovery, backed up my current ROM, then wiped Cache 3x, and Dalvik 3x, then i manually flashed the zip via install zip from SD Card, and my WiFi still errors out. So what you said is irrelevant to the issue. I appreciate your attempt to try and fix it, but the fix is not a fix.
Click to expand...
Click to collapse
Try using the newest kernel version attached to this thread. Agrabren fixed some issues and updated the kernel to a new version. Make sure to flash manually and wipe cache and dalvik cache.
I've updated the instructions and attached the newest kernel version to this thread.
MultiDev said:
Try using the newest kernel version attached to this thread. Agrabren fixed some issues and updated the kernel to a new version. Make sure to flash manually and wipe cache and dalvik cache.
I've updated the instructions and attached the newest kernel version to this thread.
Click to expand...
Click to collapse
I downloaded and flashed the kernel at 2:05pm today, the Kernel I flashed was
2.3.3-1-793-HDMwIn-Sense233-Alpha-signed.zip
Which after looking is the kernel you have attached to the OP. So that won't do it. I do believe this kernel is incompatible with Synergy+Godmode. But for the Dev's sake here is my logcat.
08-29 19:35:05.314 D/WifiStatusBarPreference(484): set wifi enable: true
08-29 19:35:05.314 D/WifiService(192): setWifiEnabled =truemAirplaneModeOverwridden =false
08-29 19:35:05.334 D/WifiService(192): setWifiEnabledBlocking:Enable Wifi
08-29 19:35:05.354 D/NetSharing_NSReceiver(1689): onReceive : android.net.wifi.WIFI_STATE_CHANGED
08-29 19:35:05.354 D/NetSharing(1689): wifi enabled change, state = false
08-29 19:35:05.354 I/WifiHW (192): wifi_load_driver enter
08-29 19:35:05.354 I/WifiHW (192): check_driver_loaded
08-29 19:35:05.354 I/WifiHW (192): insmod
08-29 19:35:05.394 D/StatusBarPolicy(484): onReceive , action=android.net.wifi.WIFI_STATE_CHANGED
08-29 19:35:05.434 I/WifiHW (192): wifi_load_driver end error 2
08-29 19:35:05.434 E/WifiService(192): Failed to load Wi-Fi driver.
08-29 19:35:05.454 D/NetSharing_NSReceiver(1689): onReceive : android.net.wifi.WIFI_STATE_CHANGED
08-29 19:35:05.454 D/NetSharing(1689): wifi enabled change, state = false
08-29 19:35:05.474 D/StatusBarPolicy(484): onReceive , action=android.net.wifi.WIFI_STATE_CHANGED
08-29 19:35:53.491 D/WifiStatusBarPreference(484): set wifi enable: true
08-29 19:35:53.491 D/WifiService(192): setWifiEnabled =truemAirplaneModeOverwridden =false
08-29 19:35:53.501 D/WifiService(192): setWifiEnabledBlocking:Enable Wifi
08-29 19:35:53.501 I/WifiHW (192): wifi_load_driver enter
08-29 19:35:53.501 I/WifiHW (192): check_driver_loaded
08-29 19:35:53.501 I/WifiHW (192): insmod
08-29 19:35:53.501 I/WifiHW (192): wifi_load_driver end error 2
08-29 19:35:53.501 E/WifiService(192): Failed to load Wi-Fi driver.
08-29 19:35:53.511 D/NetSharing_NSReceiver(1689): onReceive : android.net.wifi.WIFI_STATE_CHANGED
08-29 19:35:53.511 D/NetSharing(1689): wifi enabled change, state = false
08-29 19:35:53.531 D/StatusBarPolicy(484): onReceive , action=android.net.wifi.WIFI_STATE_CHANGED
08-29 19:35:53.531 D/StatusBarPolicy(484): onReceive , action=android.net.wifi.WIFI_STATE_CHANGED
08-29 19:35:53.541 D/NetSharing_NSReceiver(1689): onReceive : android.net.wifi.WIFI_STATE_CHANGED
08-29 19:35:53.541 D/NetSharing(1689): wifi enabled change, state = false
Ok, reflashing with 2.3.3-1-793-HDMwIn-Sense233-Alpha-signed.zip seems to have solved my issues.
Khilbron said:
I didnt use Kernel Manager to flash it, I downloaded the kernel, booted to Ra Recovery, backed up my current ROM, then wiped Cache 3x, and Dalvik 3x, then i manually flashed the zip via install zip from SD Card, and my WiFi still errors out. So what you said is irrelevant to the issue. I appreciate your attempt to try and fix it, but the fix is not a fix.
Click to expand...
Click to collapse
Not saying who is right or wrong for sure, but my wifi also did not work after flashing this from kernel manager. I wiped from recovery (dalvik and cache), and then flashed the zip from within TWRP, rebooted and everything was fixed. So for me the fix was a fix.
@ABBUB, I thanked you for your fix
madiom said:
Not saying who is right or wrong for sure, but my wifi also did not work after flashing this from kernel manager. I wiped from recovery (dalvik and cache), and then flashed the zip from within TWRP, rebooted and everything was fixed. So for me the fix was a fix.
@ABBUB, I thanked you for your fix
Click to expand...
Click to collapse
Yes but are you using synergy godmode, because that is what I am using if so, then I will temporarily flash twrp and flash the radio for a third time.
Sent from my PC36100 using Tapatalk
Khilbron said:
Yes but are you using synergy godmode, because that is what I am using if so, then I will temporarily flash twrp and flash the radio for a third time.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
I'm assuming you mean kernel when you say radio cause otherwise, you are flashing the wrong thing.
If you are still having wifi issues after flashing the latest kernel, try using the fix from here:
http://forum.xda-developers.com/showthread.php?t=1158629
That will rewrite your broken wifi driver and hopefully fix that issue.
MultiDev said:
I'm assuming you mean kernel when you say radio cause otherwise, you are flashing the wrong thing.
If you are still having wifi issues after flashing the latest kernel, try using the fix from here:
http://forum.xda-developers.com/showthread.php?t=1158629
That will rewrite your broken wifi driver and hopefully fix that issue.
Click to expand...
Click to collapse
I'll give that a shot, I also noticed that it broke 4G as well so I'm going to download it again later could be a bad download and yes I meant kernel.
Sent from my PC36100 using Tapatalk
Khilbron said:
Yes but are you using synergy godmode, because that is what I am using if so, then I will temporarily flash twrp and flash the radio for a third time.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Nope, not using Synergy, I am using MikeG. I thought I read somewhere in the Synergy forum about special flashing instructions for those using "godmode"
Awesome can't wait for this to be merged into a Tiamat kernel!
My replacement HDMI cable arrived just now so I tested it- mirroring works great on MikG 2.45
Rom (Ice Cream Sandwich):
A Near stock image, modified for a clean root, busybox install
ezAcer_AV041_A500_1.31.00_WW_GEN1_RootBusybox_S.zip
(MD5: 7e9fe5642b6e082fb4382288337d8dfa)
The long overdue update to my previous Honeycomb rom
==~== Requirements ==~==
This rom requires the unlocked ICS bootloader, I also recommend my A500 Public Recovery, however all recoverys patched for the new bootloader ought to allow installation of the rom.
Bootloader install instructions are: here thanks to civato. Note for step 4 simply ensure my update zip above is either in on the device instead of the ones listed. Note instructions below before actually flashing the rom.
Additional information can be found at Skrilax_CZ's bootloader development thread here
And my A500 Public Recovery development thread here
==~== Installing ==~==
Once you have the new bootloader and ICS recovery installed (again preferably the A500 Public Recovery but any ought to work)
Cleaning your tablet:
If you are attempting to upgrade the tablet without wiping (and there is no need to wipe if you are currently running my acer7.014.14 rooted image
Select "cleanup tab" in the main menu of the A500 Public Recovery
(If you are using another recovery, select the options for a. Wipe Cache, b. Wipe Dalvik Cache, and c. Fix Permissions)
Install the rom:
Select "install zip from sdcard" and navigate to ezAcer_AV041_A500_1.31.00_WW_GEN1_RootBusybox_S.zip
Thats it
==~== Root ==~==
Applications are granted Superuser access from ChainsDD's Superuser.apk as usual (a request asking you will appear when an application requests root, and permissions granted before the upgrade may still be active post upgrade)
adb shell: ADB by default will not have root access here you have the following options:
> if you run 'adb root' all adb operations will have root until reboot (aka 'adb shell' and 'adb remount')
> If you have a non-root 'adb shell' you can switch to root with the 'su' command
> If you wish to restore the permanent adb root on boot add the following line to the build.prop 'service.adb.root=1' this will force the old behavior of root always via adb without using the 'adb root' command.
This change has been made as its a little more secure, (However obviously still lets anyone with access to the USB port access to all the tablets data)
==~== Features ==~==
This rom is intended for users that wish a nearly stock system configuration, however either need root and busybox, or enjoy conducting more advanced tasks at the command line and wish a smooth root experience.
In addition some other small mini-fixes have been applied to the image in hope of a smooth experience.
Here is a list of the features and changes in the rom
Modified ADB to allow adb root to operate without changing the production build properties
Kernel patched to allow system remount
Busybox built from CM9 source tree and integrated into the rom
runparts (ie /system/etc/init.d functionality)
GPS lto fix thanks to waydownsouth
FDUpdater (ie system update) removed to not be prompt for an update you can't install.. if you want it the original app is in the system folder of the update.zip, (FDUpdater.apk) its not odexed so install normally)
Kernel modules md4.ko sha512_generic.ko and cifs.ko added to the rom (md4/sha512 is loaded on boot via an init.d script, users of cifs need to check the "Load cifs module" option in CifsManager.
Added Superuser
DHCP Infinite Lease bugfix (why has google not fixed this) applied as a patch to the framework.odex
Rom is still odexed (and I re-odexed the one changed odex for the DHCP patch)
Developers wanting more details or the source to anything I changed can see this detailed modification guide: http://pastebin.com/ApUjMDJ7
Note to anyone wishing to make a modification to the rom they are flashing, everything in the system folder of the update.zip is unchanged from the original rom. (when flashed the system is patched and augmented via various files and tools in the custom directory, also the boot image is pre-patched)
==~== Extras and Addons ==~==
** Overclocked test kernel: See my ezT20 kernel here (previously OCTestV3 here
(kernel last updated June 18th 2012)
** Disk IO enhancement: significantly increase diskio scores, and make the table slightly more responsive when reading/writing to flash: On this post
(diskIO last updated June 5th 2012)
==~== Tips and Tricks ==~==
This section is where I try to explain how to get the most of your tablet, and solutions to common complaints due to changes between versions.
-----) Rom "Bloat" (------
First half of what people call rom bloat is not quite true, (there is such a thing, and problems related to it)
Our tablets have 590MB system partition, a 97MB vendor partition, a 1GB cache partition, and the rest of your tablets space in a data partition (mine is 27GB, but if you have a smaller tablet model it will be less) All roms will have currently the same split between the partitions.
Its only that last partition that contains your data, the system/vendor partitions are by default read only, and the cache partition is temporary data.
System apps are on the two read only partitions, thus removing them for the most part will not cause more data to be available to your apps. Also this is storage space so having more "free" will not speed up your device (well as long as we are not too close to full.. and this rom is not)
Most of these apps play nice, they don't run unless you select them thus you can ignore they are on your tablet and all will be just as fast as if they were never installed
There is however one *Problem* Applications pre-installed that run constantly in the background that you the user are not interested in.
Solution: Freezing apps
* Goto Settings-> Apps-> All
* For any of the following that you do not use:
> Photo Browser 3D
> SocialJogger
> Acer Media
Select the app,
Choose Disable
Clear Data
If you use the app, obviously keep it enabled, also you can return to this screen and re-enable the app.
-----) Screen flickering/brightness oddities (------
I have had some brightness issues initially, simple fix was to go into settings->display->brightness uncheck auto bightness, lower the meter, and re-check auto brightness
-----) Sluggish system (------
Make sure on first boot you give the system some time (2h/3h after upgrading or re-installing where there is a large collection of media on the tablet) before measuring speed, as the system may be still sorting/indexing tablet data and will speed up when done.
Also while apps are installing the system may behave slower (if you have many market updates happening in the background)
Otherwise check running processes in settings to see if anything may be slowing down your tablet in the background (Settings -> Apps -> Running)
==~== Credits ==~==
civato - for his guide to installing the new bootloader and some testing of some of the tools I use to patch the rom up
waydownsouth - for the GPS patches (and work on CM9 for our tablets as it helped create some of the utilities in use here)
CyanogenMod and Team - For the idea of the root change, modifications to the bustybox build, and Koush's ClockworkMod recovery
vache - various insight all over XDA on how our device works (and leaks but this build is from the official OTA I recived)
Skrilax_CZ - for the unlocked bootlaoder, without which we couldn't run these roms
And the many others that provide development insight, source code, and examples here on XDA
2nd Post
reserved for future
Nice and congratulations with your release.
I will ad a link to this rom in the unlocked bootloader guide.
Overclocked kernel [May 23rd 2012]
(wow I think we can hear crickets in here..)
Anyway using the now released source code from acer, and richardtrip's OC patches from HC I now have an overclocked kernel.
As of V3 I also have the voltage controls patched up from richardtrip's kernel.
[size=+2]AcerOCTestV3_S.zip[/size]
MD5: 6907e7585fedf534261cc8ebe23d824a
Instructions are simple: flash from recovery
Links to the github source and other information on the AcerOCTest kernels is in this related notecard
While I've only tested it on this rom, the installer is using koush's anykernel logic (or one of my own flavors of that logic anyway) and thus this ought to cleanly install on any rom based on the stock ICS kernel regardless of the tweaks the rom creator may have added.)
Also I've not had much time to test so let me know if there are issues
----
List of all versions:
V3 - AcerOCTestV3_S.zip (md5: 6907e7585fedf534261cc8ebe23d824a) May 23rd 2012
V2 - AcerOCTestV2_S.zip (md5: da01a90dda3916ec55ebb62bbb1164f1) May 22rd 2012
V1 - no public binary (caused reboots on tablet sleep)
Just tried the OC kernel on Civato's latest rom and it does work. Can't go over 1.2ghz without a reboot, but that extra bit of speed is nice.
Jigga0o7 said:
Just tried the OC kernel on Civato's latest rom and it does work. Can't go over 1.2ghz without a reboot, but that extra bit of speed is nice.
Click to expand...
Click to collapse
what dosn't work? >1.2ghz or flashing it on Civato's rom
the rom ought to work, it extracts the current boot.img, swaps the zImage (leaves the ramdisk) and swaps the modules in /system/lib/modules.
as for the speed.. your device is intended for 1.0ghz any thing extra is a bonus.. the kernel thus boots at 1.0
edit: although I'll look into it some may be a new verification in the updated kernel. the tegra2 OC logic is much more complicated than the msm logic I'm used to on the HTC dream.. I'm more worried about reboot-on-wake bugs I had in earlier revisions
ezterry said:
what dosn't work? >1.2ghz or flashing it on Civato's rom
the rom ought to work, it extracts the current boot.img, swaps the zImage (leaves the ramdisk) and swaps the modules in /system/lib/modules.
as for the speed.. your device is intended for 1.0ghz any thing extra is a bonus.. the kernel thus boots at 1.0
Click to expand...
Click to collapse
Oh I said that it does work and that the only thing is can't go over 1.2ghz. We've got a nice speed bump here, thanks for your hard work.
Jigga0o7 said:
Oh I said that it does work and that the only thing is can't go over 1.2ghz. We've got a nice speed bump here, thanks for your hard work.
Click to expand...
Click to collapse
looking closer its a but..
So now I have two OC tests I've made.. the first one I didn't publish because while it could go > 1.2 it crashed when you put the tab to sleep. (at least when USB wasn't connected)
This one crashes when you go over 1.2.
maybe if a combine them I can get something that works...
Perhaps a slight voltage bump is needed to get beyond 1.2? In either case, 1.2ghz feels leaps and bounds faster than 1ghz using this rom. I'm starting to feel like we don't even need cyanogenmod 9 for the a500.
Jigga0o7 said:
Perhaps a slight voltage bump is needed to get beyond 1.2? In either case, 1.2ghz feels leaps and bounds faster than 1ghz using this rom. I'm starting to feel like we don't even need cyanogenmod 9 for the a500.
Click to expand...
Click to collapse
No.. well maybe but you not getting that far.. its a kernel BUG condition, meaning some code found some invalid input and refused to process it, instead triggered a reboot.. looking at the diff of mycode and the code in the CM thread.. no logic is different so i'll need to poke min/max rail voltages. (still sorting out all the voltages and CPU speeds.. the dream had it all in one large table .. here it seems spread out in various places between two files..)
(I'll also try to include the voltage manipulation patches just making sure things are stable first thus 1.2ghz is a better testing speed for me than trying to Max my device)
As for CM..it seems to have many interesting features.. but at some point I'm not sure its direction matches my interests.. (maybe its just become too much of a kitchen sink i don't know, that or too much now in aosp) I'm sure to look at it but probably start an aosp build with cherrypicked features I like.. until then this tweaked ics rom will need to do.
Fyi I haven't had a single issue on your kernel.
Been waiting on this! Thanks ezterry.
Jigga0o7 said:
Fyi I haven't had a single issue on your kernel.
Click to expand...
Click to collapse
Well next version will have voltage controls and working higher overclock speeds
(just ironing out some minor issues with the voltage control)
Some side info and feedback I get from some users that are on ICS bootloader and still getting SoD
I made a boot.img with in the "boot.img-ramdisk" / postboot.sh = I deleted the following line
"echo 7> /sys/module/wakelock/parameters/debug_mask" and it solves the SoD problem some still have when they are on ICS bootloader.
Just had a other pm today confirming it worked.
And I'm testing your modules and OC zImage with this modded in the boot.img-ramdisk (and my other tweaks) and I don't get any SoD , screen off , back on no problem.
Also confirming 1200 is max , over that it will reboot.
Ezterry,
Thanks!
very nice kernel, I flashed the 'civato' version to avoid SOD ...
Works nicely in 1.2 Ghz...
Btw, the old "No-Frills CPU control" apk doesn't apply the upper 1.2 Ghz frequency at Boot as asked.
Do you know another tool working to apply OC at boot?
(I'm using Civato's last version of flexreaper ROM)
=================================================================
>>>>> I have found a solution: I now use System Tuner PRO with its OC setting and it works <<<<<
=================================================================
civato said:
Some side info and feedback I get from some users that are on ICS bootloader and still getting SoD
I made a boot.img with in the "boot.img-ramdisk" / postboot.sh = I deleted the following line
"echo 7> /sys/module/wakelock/parameters/debug_mask" and it solves the SoD problem some still have when they are on ICS bootloader.
Click to expand...
Click to collapse
.. I think this solution has nothing to do with the debug variable and everything to do with *forcing* the user to install a ICS kernel and stop messing around with the HC kernel they had earlier. (since you are installing a new boot.img)
So says the code anyway. If you want to prove it wrong after the crash + quick reboot get your users to dump the last_kmsg and output of dmesg so we can actually debug what is going on.. well unless its just the wrong kernel
But if the "obecalp" works to get some your users to install the right thing and so they fix there own problem.. so be it.
--
I have to inform users of my rom its no longer my rom if they install one of your (or anyone else's) full boot images and not to complain of any resulting bugs here.. If anyone with this rom has a SoD (none reported yet.. but I block installation on the old HC bootloader) let us know if you have such an issue. (just want to add if the full boot image was modified from the one in this rom, and intended for users of this rom that isn't an issue.. the issue is when its for another rom)
Its a bit different when you flash my update on another rom, since I only swap the kernel and leave the ramdisk as is, (by unpacking and repacking the boot.img) the rom designers changes stay intact.. well unless they had a kernel module that I've not included.. but even then we will need to re-build that module)
and you can test this after boot enter terminal and run echo '3> /sys/module/wakelock/parameters/debug_mask' that is the default.
(If it is disabled it just won't print the list of wakelocks to the kernel log on suspend..)
UPDATE @@
http://forum.xda-developers.com/showpost.php?p=26432810&postcount=4
ezterry said:
[size=+2]AcerOCTestV3_S.zip[/size]
MD5: 6907e7585fedf534261cc8ebe23d824a
Click to expand...
Click to collapse
Hopefully fixed the max speed bug, and added in the voltage controls.
Not much else yet has changed. but seems stable.
Its the same anykernel package as last time so it should cleanly swap the kernel (leaving the previous ram disk) for any ICS stock kernel based rom.
(Is there one app out there that actually knows how to successfully set *both* cores frequency and set voltage on boot, without giving the world access to the /sys files [so a malicious app cant overclock+fry the device or under clock it so it feels painfully slow]... soon I'll just write an init.d script for myself to echo the values directly into the kernel settings /rant)
I use setcpu.
civato said:
I use setcpu.
Click to expand...
Click to collapse
I don't like that he (and has always) granted global write permissions to the /sys/ files controlling the CPU/Voltage settings .. and it was acting flaky on voltage settings on boot.
Voltage Control looked good until a verification in /sys indicated if left the second CPU core at 1GHz
Now poking system tuner/system tuner pro.. many interesting features. Not sure they quite understand use root to write the value.. or set the file to your own ownership..
*ANYWAY*
you can check these yourself manually at the command line/adb shell:
CPU0: /sys/devices/system/cpu/cpu0/cpufreq
CPU1: /sys/devices/system/cpu/cpu1/cpufreq
current status of the voltages is in the readonly: frequency_voltage_table
list readonly of available frequencies is: scaling_available_frequencies
list readonly of available governors: scaling_available_governors
the current min frequency: scaling_min_freq
the current max frequenct: scaling_max_freq
the current cpu governor: scaling_governor
the current undervolt levels (negative values are over volting): UV_mV_table
UV_mV_table is in the same order as frequency_voltage_table, and if written to with the same number of values will update the voltage levels.
I got a question , why :
sha512_generic.ko = what does this do ?
modules.order = why does it need to know the order ?
Hello all Forum Users.
Unfortunately I'm not yet allowed to post on Android Development, so I have to write here.
I would be gratuful if someone could post a link there or permit me to write there:
http://forum.xda-developers.com/showthread.php?t=2180085
I'm quite experienced FreeBSD kernel developer and I would like to get involved into pinkflozd CM kernel development.
I'm almost newbe to Linux kernel but I think there are some problems with WiFi on e610 devices.
I have the latest CM 10 with pinkflozd CM kernel v0.70.
Everything seems to work OK except from the Wifi.
When the WiFi is off, "lsmod" shows only "frandom" module - it's OK.
When I turn the WiFi on, "lsmod" shows also "librasdioif" and "wlan" modules loaded
but the WiFi is unable to turn on and the modules are unloaded soon.
"dmesg" show some info (not including everything):
- wlan0: link is not ready (many times)
- init: untracked pid xxxx exited
- wlan: unloading driver v0.2.2.542
- <many other errors>
- libra sdio remove : Module removed.
I also tried "l5_wifi_fix" - it didn't help.
I can send more debug info if required. I am not familiar with the Android "log" subsystem.
I have a problem with the 3G Data Connection. The WiFi is working fine, sorry I can't help about it. I just didn't know where to ask my question. How can i fix data connectivity? before flashing CM10, on original ICS it was working just fine. I also tried flashing only the ROM without the pinkflozd kernel, still no connectivity. In settings its set on "allowed" or whatever it says. Please help. :/
l5_wifi_fix must be started from PC, there is fix.cmd, of course phone must be connected by USB
Andro995 said:
I have a problem with the 3G Data Connection. The WiFi is working fine, sorry I can't help about it. I just didn't know where to ask my question. How can i fix data connectivity? before flashing CM10, on original ICS it was working just fine. I also tried flashing only the ROM without the pinkflozd kernel, still no connectivity. In settings its set on "allowed" or whatever it says. Please help. :/
Click to expand...
Click to collapse
I'm afraid I can't help. Everyone says that 3G Data Connection starts working after the second reboot.
Try reboot and then run "dmesg" from the terminal. Scroll it and try to find something which might be useful to solve the problem.
twisted_tits said:
l5_wifi_fix must be started from PC, there is fix.cmd, of course phone must be connected by USB
Click to expand...
Click to collapse
Thanks, I know it. I've rewritten the script so it could be executed from Linux.
Some dmesg output
I have something like that when booting PinkFlozd kernel:
<4>[ 23.496161] ------------[ cut here ]------------
<4>[ 23.496248] WARNING: at arch/arm/mach-msm/clock.c:196 clk_disable+0x138/0x148()
<4>[ 23.496274] ebi_grp_3d_clk is unbalanced
<4>[ 23.496288] Modules linked in: wlan(P) librasdioif frandom
<4>[ 23.496351] [<c00467c4>] (unwind_backtrace+0x0/0x138) from [<c00d5e00>] (warn_slowpath_common.constprop.7+0x4c/0xd0)
<4>[ 23.496391] [<c00d5e00>] (warn_slowpath_common.constprop.7+0x4c/0xd0) from [<c00d5ea8>] (warn_slowpath_fmt+0x24/0x34)
<4>[ 23.496428] [<c00d5ea8>] (warn_slowpath_fmt+0x24/0x34) from [<c00569c4>] (clk_disable+0x138/0x148)
<4>[ 23.496466] [<c00569c4>] (clk_disable+0x138/0x148) from [<c046dd9c>] (_sleep+0x108/0x3ec)
<4>[ 23.496499] [<c046dd9c>] (_sleep+0x108/0x3ec) from [<c046eadc>] (kgsl_idle_check+0x154/0x1c8)
<4>[ 23.496538] [<c046eadc>] (kgsl_idle_check+0x154/0x1c8) from [<c00f0d44>] (process_one_work+0x1ec/0x354)
<4>[ 23.496573] [<c00f0d44>] (process_one_work+0x1ec/0x354) from [<c00f10a0>] (worker_thread+0x1c8/0x308)
<4>[ 23.496608] [<c00f10a0>] (worker_thread+0x1c8/0x308) from [<c00f6b0c>] (kthread+0x84/0x8c)
<4>[ 23.496646] [<c00f6b0c>] (kthread+0x84/0x8c) from [<c0040e9c>] (kernel_thread_exit+0x0/0x8)
<4>[ 23.496673] ---[ end trace a139245ee3e508ee ]---
It might be the reason why WiFi doesn't work.
kkarpowi said:
Thanks, I know it. I've rewritten the script so it could be executed from Linux.
Click to expand...
Click to collapse
BTW - Running l5_wifi_fix results are:
modprobe: 'librasdioif.ko': invalid module format
modprobe: 'wlan.ko': invalid module format
WiFi working
WiFi is working after a total wipe and CM10-20130414 installed.
I don't know what was wrong or if anything was fixed. Really don't know.
PinkFlozd kernel and gapps also installed and still OK.
I hope that everything else is working fine - checking...
I recommend to update your stock firmware to V20A_Rooted.kdz. Its very smooth and runs my Temple run 2 whith no lags on 800mhz.
Link for the kdz update:
http://forum.xda-developers.com/showthread.php?t=2230679
Link for the 4.1.2 Clean rom v2:
http://forum.xda-developers.com/showthread.php?t=2232123
jannick63 said:
I recommend to update your stock firmware to V20A_Rooted.kdz. Its very smooth and runs my Temple run 2 whith no lags on 800mhz.
Link for the kdz update:
http://forum.xda-developers.com/showthread.php?t=2230679
Link for the 4.1.2 Clean rom v2:
http://forum.xda-developers.com/showthread.php?t=2232123
Click to expand...
Click to collapse
That's what I did yesterday. And AFTER that (and of course after reinstalling the latest CM10 from scratch) WiFi started working. Strange, isn't it?
my sim card is not working
Andro995 said:
I have a problem with the 3G Data Connection. The WiFi is working fine, sorry I can't help about it. I just didn't know where to ask my question. How can i fix data connectivity? before flashing CM10, on original ICS it was working just fine. I also tried flashing only the ROM without the pinkflozd kernel, still no connectivity. In settings its set on "allowed" or whatever it says. Please help. :/
Click to expand...
Click to collapse
my sim card is not working
you should try flashing baseband,specify which base band you are in now
Sent from my LG-P700 using xda app-developers app
OP, if you want to help pm pinkflozd. And I think you need to post at least 10 times to be able to post on development forum.
So just keep posting on this thread
on my p705g - vanir rom
ULTRA Kernel installer is an AIO kernel tool that uses AROMA installer (what's that?).
This tool is capable to backup, install ULTRA kernel, and restore a kernel backup.
Make a Nandroid backup before using it, to stay safe.
ULTRA kernel features
+ OC support
+ Lot of governors and schedulers added:
-- New governors --
Hotplug
ZZmove
OndemandQ
LulzactiveQ
Smartassv2
InteractiveQ
-- New schedulers --
BFQ
ROW
ZEN
VR
+ PhilZ Recovery (what's that?). Thanks Phil3759!
DOWNLOAD
Android File Host
Dev-Host
Thanks @iiD4x for the idea and logo. And @AndyMcMars!, he spent lot of time on this too.
XDA:DevDB Information
ULTRA Kernel Installer, Kernel for the Samsung Galaxy S Advance I9070
Contributors
t4n017, cocafe, Phil3759, TeamCanjica, TeamNova, AndyMcMars, iiD4x
Kernel Special Features:
Version Information
Status: Beta
Created 2014-03-18
Last Updated 2014-05-28
Changelog
CHANGELOG
20140401 (v4.01)
- Deleted all previous kernels varieties
- Added an all-in-one kernel (called ULTRA)
- Now the installer is compatible with CM-11 users too (choose the right option when prompted)
- UKSM is back (KSM --> UKSM) [testing]
- UKSM now disabled by default
- Added UKSM toggle in Galaxy S Advance settings (advance tab)
- PhilZ recovery updated (v6.25.4)
---x---x---x---
20140328 (v3.28)
- KSM is back (UKSM --> KSM)
- Fixed Aroma FM copy process
- PhilZ recovery updated (v6.24.6)
---x---x---x---
20140325 (v3.25)
- Kernel sources update (lot of performance improvements!)
- PhilZ recovery updated (v6.23.3)
- Script a bit more clean
---x---x---x---
20140323 (v3.23)
- Fixed modules install/restore process. (NOW REALLY!)
---x---x---x---
20140320
- Fixed modules restore process.
---x---x---x---
20140319C
- Now the script will also backup modules files (thanks @darcik for the suggestion).
---x---x---x---
20140319B
- All kernels were rebuilt from scratch
- No more Wi-Fi bug!
- Added Smartassv2, InteractiveQ and Interactive to PLUS (and therefore PLUS+OC) kernel.
---x---x---x---
20140319A
- Temporary deleted PLUS and PLUS+OC due to Wi-Fi bug.
---x---x---x---
20140318
- Initial build
---x---x---x---
Reserved
Very good, I waiting PhilZ Kernel a long time xD
Thank you!
Well, after lot of test I think the Wi-Fi bug is only happening on PLUS and, therefore, PLUS+OC kernel.
It's weird because I didn't touch anything related to Wi-Fi.
I apologize to those who installed them, and further to those who tried the alternative installation method without result.
I'll built them again from scratch and report back.
"I told you..." :victory:
Is the OC kernel stable? Is it possible to under volt?
fbs said:
"I told you..." :victory:
Click to expand...
Click to collapse
Yes, but lot of user reported PLUS was working fine. Maybe they thought they were installing PLUS but instead, they were restoring the default kernel backup.
marlock87 said:
Is the OC kernel stable? Is it possible to under volt?
Click to expand...
Click to collapse
Not all the Advances can handle the same freq, you should try if you can OC without reboots.
It should be, but I didn't tested UV. If you do, please report
Philz Kernel working fine in RR 5.0.5
i flashed philz kernel on cm11 05/03 build(dalvik runtime).it installed fine but after restarting i always get process.android,phone has stopped.even factory reset including wipe dalvik cache wouldnt resolve the issue.flashing the beanstalk rom since i wanted to try it out anyway.the recovery work fine though including power off(the feature which is actually why i installed it in first place).anyways thanks bringing the kernel for our device and hoping to see more development:good:
wingryder said:
i flashed philz kernel on cm11 05/03 build(dalvik runtime).it installed fine but after restarting i always get process.android,phone has stopped.even factory reset including wipe dalvik cache wouldnt resolve the issue.flashing the beanstalk rom since i wanted to try it out anyway.the recovery work fine though including power off(the feature which is actually why i installed it in first place).anyways thanks bringing the kernel for our device and hoping to see more development:good:
Click to expand...
Click to collapse
for now , PhilZ wont work on CM ..
I get the "process.android,phone has stopped" error after installing (wipe cache, wipe, dalvik, install zip), and I used the DEFAULT kernel. Why?
I use Carbon KitKat rom,
So happy to see this topic, thanks for posting!
GREAT NEWS!
I've built all the kernels from scratch, now Wi-Fi bug is fixed! Please test and report.
Check changelog for more changes.
Are these kernels supposed to work with the i9070-P version??? Just to be sure...
elementbt said:
Are these kernels supposed to work with the i9070-P version??? Just to be sure...
Click to expand...
Click to collapse
Yes ofc, when you flash a ROM (like RR) you're using the DEFAULT kernel posted here.
Just installed DEFAULT KERNEL and I get the "process.android,phone has stopped" error.
Nothing helped.
CM 11 by Macław.
darcik said:
Just installed DEFAULT KERNEL and I get the "process.android,phone has stopped" error.
Nothing helped.
CM 11 by Macław.
Click to expand...
Click to collapse
It seems that the kernels aren't working fine on CM 11. I don't know why, but I'll ask TeamCanjica for help.
Tnx for fast answer.
Btw, your script is making backup of kernel and coping new modules to system/modules folder,
but if is needed restore old kernel, modules files are new and is problem because they are not working with old kernel
Good, that I did myself copy of these files.
darcik said:
Tnx for fast answer.
Btw, your script is making backup of kernel and coping new modules to system/modules folder,
but if is needed restore old kernel, modules files are new and is problem because they are not working with old kernel
Good, that I did myself copy of these files.
Click to expand...
Click to collapse
Thanks for report bro!, I forgot the modules backup. Anyway you can use DEFAULT kernel to restore them.
But I'll edit the script to backup those files and I'll re-upload them.
Really thank you!
Hi,
1. I try to patch kernel for nethunter "porting nethunter" google. Watching yt video "compile nethunter kernel". At the point ~min6-8 he chooses config to change and got only one in configfolder. I have many, which one is the right?
2. I get error compiling kernel adressed to scripts/gcc-version.sh "oserror: invalid number, exec: invalid number..etcetc: invalid number..
3. Is it possible to do 64 kernel on 32 bit machine?