Hey there guys,
I found these drivers http://forum.xda-developers.com/showthread.php?t=2238348, but they are not suitable ATM.
Sorry for making you all happy with something that doesn't work. Let's make a good discussion about how we can instead make all this work.
steyn_e said:
Hey there guys,
I found these drivers http://forum.xda-developers.com/showthread.php?t=2238348 for our Sensations, which solves the graphical glitches in Google Maps 7. Please all use these in your ROM's. I also found an even newer version, but that is not compatible with the Linux kernel we are currently using (3.0.x).
The build number for these are [JB_VANILLA.04.02.02.060.053]. These need a 3.4.x kernel.
I hope you can all enjoy these! The package can be downloaded here.
You can simply be flash it through 4ext, afterwards clear dalvik+cache.
Have fun!
Click to expand...
Click to collapse
If they need a 3.4.x kernel you need to state clearly that they are for JB sense. None of the aosp jb roms here use a 3.4.x kernel.
sjknight413 said:
If they need a 3.4.x kernel you need to state clearly that they are for JB sense. None of the aosp jb roms here use a 3.4.x kernel.
Click to expand...
Click to collapse
Only the latter ones (which I didn't include a link for) are for 3.4.x. The ones linked work for 3.0.x, and I am using them now on CM10.2. They will also work on CM10.1, and maybe on CM10 if the kernel is 3.0.x or over. I'll try to find a link for the other ones for people using a Sense based ROM.
Okay, I made myself clear. The first download is for kernel 3.0.x (tested on CM10.2 and working), the second download is for kernel 3.4.x (and maybe further), but I cannot test that as I am not using a Sense based ROM. It is sourced directly from Qualcomm.
Now I'm thinking of it: we should probably make a list of compatible kernels for the different drivers. I'm using the Albinoman 3.0.100 kernel.
Sad to say, but I've still got glitches.. Installed with 4Ext and wiped cache + dalvik cache.
Albinoman's 4.3.1 26-10 with his kernel.
84Guzz said:
Sad to say, but I've still got glitches.. Installed with 4Ext and wiped cache + dalvik cache.
Albinoman's 4.3.1 26-10 with his kernel.
Click to expand...
Click to collapse
You did install the upper one? Which version of Maps are you using?
Also, what is the Linux kernel version of your rom (in device info)?
Let's make this work...
steyn_e said:
You did install the upper one? Which version of Maps are you using?
Also, what is the Linux kernel version of your rom (in device info)?
Let's make this work...
Click to expand...
Click to collapse
Yes, I got the one for a 3.0 kernel
Maps: 7.3.0
Kernel version: 3.0.100
The glitches are not as bad as they used to be, but try drawing the notification bar. Also the dialog to turn on GPS when starting navigation will flicker.
Edit: Press the "go to my location" button (top right) it will prompt a dialog to turn on GPS, which will flicker between opaque and transparent
84Guzz said:
Yes, I got the one for a 3.0 kernel
Maps: 7.3.0
Kernel version: 3.0.100
The glitches are not as bad as they used to be, but try drawing the notification bar. Also the dialog to turn on GPS when starting navigation will flicker.
Edit: Press the "go to my location" button (top right) it will prompt a dialog to turn on GPS, which will flicker between opaque and transparent
Click to expand...
Click to collapse
Tried it. It does the same with me once, but the second time it didn't. And just moving through maps doesn't glitch anymore.
steyn_e said:
Tried it. It does the same with me once, but the second time it didn't. And just moving through maps doesn't glitch anymore.
Click to expand...
Click to collapse
Do you mean you tried the notification bar? This keeps glitching with me.
Moving trough maps is OK indeed.
I've now modded the 2nd set of drivers to install on my device, let's see how this goes.
A few things:
1. These libs don't boot. If they "booted" for you then that's because the installer never installed them. The line in the updater script to mount /system makes it try and mount system as a yaffs2 partition, but we don't use yaffs2 we use ext4, so /system is never actually mounted. I modified the installer so it actually installs the libs and they do not boot. Some more proof of this is that the zip flashes very quickly, when it should actually take about 10-15 seconds to flash. They probably require a kernel with ION and a GPU driver from a 3.4 kernel.
2. Our Maps glitches are not being caused by our Adreno libs. Read my post HERE
3. The package for 3.4 kernels is not a flashable zip.
4. The package for 3.4 kernels does not necessarily require a 3.4 kernel (I have booted them on a 3.0 kernel); all they require is a kernel with a GPU driver from a 3.4 kernel and ION.
android1234567 said:
A few things:
1. These libs don't boot. If they "booted" for you then that's because the installer never installed them. The line in the updater script to mount /system makes it try and mount system as a yaffs2 partition, but we don't use yaffs2 we use ext4, so /system is never actually mounted. I modified the installer so it actually installs the libs and they do not boot. Some more proof of this is that the zip flashes very quickly, when it should actually take about 10-15 seconds to flash. They probably require a kernel with ION and a GPU driver from a 3.4 kernel.
2. Our Maps glitches are not being caused by our Adreno libs. Read my post HERE
3. The package for 3.4 kernels is not a flashable zip.
4. The package for 3.4 kernels does not necessarily require a 3.4 kernel (I have booted them on a 3.0 kernel); all they require is a kernel with a GPU driver from a 3.4 kernel and ION.
Click to expand...
Click to collapse
Yes, I've noticed the META-INF was missing in the 2nd one. However, it did do something. Maps is not even nearly as glitchy as it was. It only glitches now if something pops in front (like that "do you want to enable GPS" or the notification bar).
Our Adreno drivers want ION, and the camera wants PMEM, however is it even close to possible to make the camera libs work with ION?
steyn_e said:
Yes, I've noticed the META-INF was missing in the 2nd one. However, it did do something. Maps is not even nearly as glitchy as it was. It only glitches now if something pops in front (like that "do you want to enable GPS" or the notification bar).
As it is nearly impossible to rewrite the Adreno libs to use PMEM, is it even close to possible to make the camera libs work with ION?
Click to expand...
Click to collapse
Sebastian modified VilleC2 camera libs to work with our camera sensor and rewrote the camera driver, but Sebastian is on a whole different level from me
Also, the first package did absolutely nothing. I tested it and nothing was flashed to /system because the installer couldn't mount /system (because it's trying to mount /system as yaffs2). My Adreno version did not change, and when I fixed the package to install correctly, my phone did not boot (as they probably require ION and a 3.4 GPU driver; my kernel has a 3.4 GPU driver but ION is still necessary to get them booting). There's no such thing as in between with these Maps glitches; the glitches are either there or they're not.
android1234567 said:
Sebastian modified VilleC2 camera libs to work with our camera sensor and rewrote the camera driver, but Sebastian is on a whole different level from me
Also, the first package did absolutely nothing. I tested it and nothing was flashed to /system because the installer couldn't mount /system (because it's trying to mount /system as yaffs2). My Adreno version did not change, and when I fixed the package to install correctly, my phone did not boot (as they probably require ION and a 3.4 GPU driver; my kernel has a 3.4 GPU driver but ION is still necessary to get them booting). There's no such thing as in between with these Maps glitches; the glitches are either there or they're not.
Click to expand...
Click to collapse
So I've noticed. Isn't Sebastian's kernel ION?
steyn_e said:
So I've noticed. Isn't Sebastian's kernel ION?
Click to expand...
Click to collapse
Yes. Sebastian's kernel satisfies all the requirements to use these libs (ION and 3.4 GPU driver) so they should boot on any ROM using his kernel.
android1234567 said:
Yes. Sebastian's kernel satisfies all the requirements to use these libs (ION and 3.4 GPU driver) so they should boot on any ROM using his kernel.
Click to expand...
Click to collapse
Now the final thing is obviously to make that kernel work with your ROM. Possible at all?
steyn_e said:
Now the final thing is obviously to make that kernel work with your ROM. Possible at all?
Click to expand...
Click to collapse
Even if I managed to get all the basic things working (which I don't think I can do), getting the camera working would be a problem and we'd probably be forced to use PMEM on the whole kernel (which would defeat the purpose of a 3.4 kernel).
android1234567 said:
Even if I managed to get all the basic things working (which I don't think I can do), getting the camera working would be a problem and we'd probably be forced to use PMEM on the whole kernel (which would defeat the purpose of a 3.4 kernel).
Click to expand...
Click to collapse
That means there is no hope for getting every single thing to work on our phones?
steyn_e said:
That means there is no hope for getting every single thing to work on our phones?
Click to expand...
Click to collapse
Man, we are running android 4.3 on phone which was officialy updated to 4.0 only. That is normal that some thing arent working
Wysłane z mojego HTC Sensation przy użyciu Tapatalk 4
szotaa said:
Man, we are running android 4.3 on phone which was officialy updated to 4.0 only. That is normal that some thing arent working
Wysłane z mojego HTC Sensation przy użyciu Tapatalk 4
Click to expand...
Click to collapse
That doesn't mean we shouldn't try. I'd love to learn more about this stuff. And if someone can teach me, we Sensation users will have another driven Devver. I won't be able to do this on my own however, as it has been too long since I've last been devving for a Phone (that was my Touch Pro 2).
Related
OK, here is the latest update. Instead of using kernel extracted from Rogers stock ROM, I compiled HTC kernel source downloaded from developer.htc.com.
To make touch screen work, one has to update sapphire_defconfig. Only one configuration has to be changed -- that is, to make the following unset.
#CONFIG_TOUCHSCREEN_CONCATENATE_REPORT=y
Then, compile kernel as usual and touch screen works with AOSP Froyo.
Hopefully, the above information is useful. Wifi is fine. But, camera is not working.
==================================
Guys, help is needed here.
In the past two weeks, I tried to compile AOSP Froyo (branch 2.2_r1) with HTC kernel (2.6.29) extracted from Rogers stock ROM. The compilation went fine. Boot also went smoothly until it reaches the screen that requires users to enter PIN code. At the moment, I found that I CANNOT enter anything from screen. (touch screen is gone)
As far as I can tell from the android architecture, touch screen is something related to kernel, right? HTC kernel does support touch screen. So, I was lost???
I tried to read init.rc, init.sapphire.rc, and init.goldfish.rc, and system/etc/ files to see if I missed some configurations. But found nothing.
What should I do? Any help is appreciated.
the driver in the kernel .29 do not fit the android 2.2 you need a different kernel, i got touchscreen by using the .34 kernel from froyorider
sharpt71 said:
Guys, help is needed here.
In the past two weeks, I tried to compile AOSP Froyo (branch 2.2_r1) with HTC kernel (2.6.29) extracted from Rogers stock ROM. The compilation went fine. Boot also went smoothly until it reaches the screen that requires users to enter PIN code. At the moment, I found that I CANNOT enter anything from screen. (touch screen is gone)
As far as I can tell from the android architecture, touch screen is something related to kernel, right? HTC kernel does support touch screen. So, I was lost???
I tried to read init.rc, init.sapphire.rc, and init.goldfish.rc, and system/etc/ files to see if I missed some configurations. But found nothing.
What should I do? Any help is appreciated.
Click to expand...
Click to collapse
I bet that you have a MyTouch with a 3.5mm headphone jack huh?
If not then you need to include more information.
In regards to the 3.5mm headphone jack version (also known as Fender or 1.2) it has slightly different hardware drivers that require the patch made by Voxluna. Most developers include this in their roms by default however if you are using any other source then odds are that they won't include the patch thus creating your problem.
capychimp said:
the driver in the kernel .29 do not fit the android 2.2 you need a different kernel, i got touchscreen by using the .34 kernel from froyorider
Click to expand...
Click to collapse
Since HTC source code was just released, will you please point me to the right files/folders so that I can find out the reasons why .29 does NOT work with Froyo?
I had once compiled AOSP Froyo with HTC kernel .27 by following instructions on http://www.lingnu.com/en/howto/72-android-aosp-htc-32a.html. Although camera (and maybe other devices) did not work, touch screen worked fine. Due to this experience and the limited reading of android architecture, I thought I could simply replace the kernel without affecting other layers. Hmm, to use layers design, why didn't google keep APIs intact?
Binary100100 said:
I bet that you have a MyTouch with a 3.5mm headphone jack huh?
If not then you need to include more information.
Click to expand...
Click to collapse
Sorry for not making this clean in the first place. Mine is a 32A which is running Rogers stock rom with root (made by capychimp) + chinese support + htc_cime (cooked by myself).
Ciompilation involved roughly the follwings:
1. AOSP froyo branch 2.2_r1
2. Comppilation of Froyo by following http://xy0811.spaces.live.com/blog/cns!F8AECD2A067A6B17!1526.entry?wa=wsignin1.0&sa=474748515 (which is similar to dferreira's howto)
3. unziped capy's Rogers_21_capychimp.zip instead of signed-google_ion-ota-14721.zip.
4. extracted kernel and wlan.ko from the boot.img in Rogers_21_capychimp.zip
the source from htc is for sense roms, way different drivers. I have a perfect .34 kernel for froyo but no cam so far.
carz12 said:
the source from htc is for sense roms, way different drivers. I have a perfect .34 kernel for froyo but no cam so far.
Click to expand...
Click to collapse
Thanks for the info. I just updated the current status at the 1st post.
From what I did, I kind of wondering whether or not the not-working camera problem is related to "configurations" because camera works on 2.1. But, I am not a kernel guy and will not be one.
sharpt71 said:
Then, compile kernel as usual and touch screen works with AOSP Froyo.
Click to expand...
Click to collapse
A screenshot of software information is attached. Oh, sdcard cannot be mounted unless it has no ext/swap partitions.
nice on the touch screen, will come in handy thx will try it on my wildfire port
It seems that finally I was able to boot custom kernel with working radio
It's not very stable yet(it stops/crashes at bootanimation quite frequently), and is quite laggy just after boot, but once it boots it seems to be almost usable. Wifi works, sdcard also. Haven't checked bluetooth.
Credits for this goes to:
* milestone1 devs... for sharing 2ndboot source code and providing so much info regarding milestone1/2 phones
* Motorola ... for providing source code(not fully working, but was a great help anyway) for enabling UART over micro usb for debugging purposes(without this I woudn't make any progress)
* tezet... for making quite good roms used by 2ndboot
If you wish to try it(BEWARE THAT IT MIGHT BRICK YOUR PHONE, SO DON'T SAY THAT I HAVEN'T WARNED YOU ), then do as follows:
1. Install tezet's JB10(if you don't have one already).
2. extract 2ndboot.tar(attached) into /data folder, check that /data/2ndboot/hbootuser file has execute permissions.
3. overwrite /system/bootmenu/script/2nd-boot.sh(DON'T TOUCH 2nd-init.sh!!!) with the one from tar(2nd-boot.sh.tar) and check it has execute permissions.
4. reboot into bootmenu
5. change the default boot method to 2ndboot
6. Restart your phone. Most likely it will crash few times at bootlogo, but be patiant, it finally should boot
7. If you wish to get back to 2nd-init, then enter bootmenu again and change default boot method back to 2nd-init, or manually boot 2nd-init
Click to expand...
Click to collapse
Please let me know if someone actually run it and was able to boot(so that to find out if I haven't forgot to include some more files(see changelog for 03.10.2012)
KNOWN LIMITATIONS
Boots very sloooowly
Its' quite laggy just after boot.
GPS does not seem to work yet
Click to expand...
Click to collapse
CHANGELOG
01.10.2012 - corrected battery problems(thanks to Quarx and kabaldan)
03.10.2012 - corrected ramdisk(previous one was calling some script which I forgot to attach to this post, new one has this script inside), so that now you should be able to boot it; updated instructions how to install it; enabled TLS in the kernel(thanks to kabaldan)
04.10.2012 - touch driver updated, now should work with lastest JB(thanks to Eleanor_Ir, Quarx), adb fixed(I hope, stability fix(thanks to Quarx)
Click to expand...
Click to collapse
NOTES for devs
In milestone2(as probably in many others UMTS phones made by Motorola) the BP is somehow very sensible and does not like to be disconnected/reenumerated. The main goal of this 2ndboot is then to not allow it to be disconnected. To do this, in the new kernel I've skipped a few resets(EHCI, TLL, individual port resets), and instead of enumerating BP, I've used the hardcoded usb device address(which for milestone2 seems to be equal to 2).
I attach patch(radio.patch) with the changes I've done to the kernel sources from here:
http://sourceforge.net/projects/milestone.motorola/files/MILS2_U6_4.1-22/
This seems to work(sometime) for both milestone2 and defy.
For other motorola phones:
1. First of all, check with lsusb what's the address and vendor/product id of your BP(for milestone2 it's 0x22b8 and 0x40e6).
2. If the BP usb device address is 2, then just apply the patch(probably it will need some small modifications), and check if it works.
3. If the BP usb device address is not 2, then edit usb/core/hub.c function hub_port_init(providing that it's there for your kernel), and replace 0x02 in the place where usb_control_msg to get descriptors is sent with address of your device
If it does not work, then you can try the following:
Create a procedure to send usb GetDescriptors request using omap3 ehci registers, and call it at different boot stages/usb initialization stages to find out how long the radio remains attached, and comment/change appropriate fragments of kernel code, to preserve this until usb port is initialized. If you wish, I can share the procedure I've written(in the patch file this is that czecho_get_descriptors called in many places) for milestone2, but it probably would need some modification to work with your device).
2ndboot module sources are here:
https://github.com/czechop/2ndboot
Wow, thats perfect This could bring M2 development to another level.
Holding thumbs up and keep it up!
Great news! Thx for your work. I've just bought an OTG cable to start playing with kernel stuff and here's a surprise
Fabulous! That means it starts a new era in the development of our MS2 Roms!
Wonderful job man
Brilliant
Sent from my A953 using Tapatalk 2
I'm gonna try on the Motorola Bravo as soon as PA is done uploading. Hopefully this'll work on Froyo kernels as well :fingers-crossed:
What kernel are you using? A recompiled MS2 GB kernel unmodified?
Awesome job man. This could possibly be the start of a new generation of roms for our common platform if this works on other similar phones like the Defy\Bravo. Only time will tell .
Well good work OP, can this be implemented on other Moto phones like Defy?
Great work !
I see that your work is based on Moto's Linux kernel (2.6 branch as far as I remember...)
Any hope of using another kernel source one day ?
Great News!, Thanks
Waiting for source code
Wow! Tezet and Quarx on the same thread?! I feel like up on the Mount Olypmus lol
Great job, man!...been following your work from General section.
P.S. add Kabaldan to the list Clash of the Moto Titans
skeevy420 said:
I'm gonna try on the Motorola Bravo as soon as PA is done uploading. Hopefully this'll work on Froyo kernels as well :fingers-crossed:
What kernel are you using? A recompiled MS2 GB kernel unmodified?
Awesome job man. This could possibly be the start of a new generation of roms for our common platform if this works on other similar phones like the Defy\Bravo. Only time will tell .
Click to expand...
Click to collapse
Yes, I use MS2 GB U6_4.1-22(http://sourceforge.net/projects/milestone.motorola/files/MILS2_U6_4.1-22/) kernel... but with modified usb host driver.
nidhish91 said:
Well good work OP, can this be implemented on other Moto phones like Defy?
Click to expand...
Click to collapse
I think it can be.
With defy it probably should be easy, as I've seen there was 2ndboot(without radio) already build for it, so most likely only new kernel would need some tuning
czechop said:
I think it can be.
With defy it probably should be easy, as I've seen there was 2ndboot(without radio) already build for it, so most likely only new kernel would need some tuning
Click to expand...
Click to collapse
XT720 users also waiting for instructions for new kernel tuning, cause we have working 2ndboot without radio. =)
boorce.com said:
Great work !
I see that your work is based on Moto's Linux kernel (2.6 branch as far as I remember...)
Any hope of using another kernel source one day ?
Click to expand...
Click to collapse
It should be easy to apply some(perhaps most) 2.6.32 upstream patches to the motorola kernel sources.
Don't know however how difficult it would be to start from another kernel version. Don't know also how motorola proprietary modules/libs would behave with newever kernel version. But, as they say, impossible is nothing
czechop said:
I think it can be.
With defy it probably should be easy, as I've seen there was 2ndboot(without radio) already build for it, so most likely only new kernel would need some tuning
Click to expand...
Click to collapse
In kernel only modified usb driver or some more changes for boot?
fjfalcon said:
XT720 users also waiting for instructions for new kernel tuning, cause we have working 2ndboot without radio. =)
Click to expand...
Click to collapse
Will share source code probably early next week(currently am at work, and during weekend most likely won't be sober enough
Quarx said:
In kernel only modified usb driver or some more changes for boot?
Click to expand...
Click to collapse
In 2ndboot module I've added code to disable lcd before starting new kernel(otherwise new kernel could not initialise properly dss), and in new kernel I've only modified usb driver(perhaps more things will need to be modified, as I'm facing problem with BATTD sayins something about power ic fail, BTW, does someone know what that could mean?), so that it skips restaring EHCI, TLL and don't start enumeration, but just used the old usb device address(assigned by the original kernel), which for M2 is always 2(at least during my tests).
I2c Fail can be caused by wrong permissions for /dev/cpp*
I tried your prebuilt binaries on defy http://pastebin.com/jKjQ2ykn
Black screen + buttons lights and reboot after ~20sec
Quarx said:
I2c Fail can be caused by wrong permissions for /dev/cpp*
I tried your prebuilt binaries on defy http://pastebin.com/jKjQ2ykn
Black screen + buttons lights and reboot after ~20sec
Click to expand...
Click to collapse
Thanks for hint regarding permissions...will check that
Regarding prebuilt binaries on defy, hard to say what's wrong(not sure how much the phones differ). Anyway, you probably would need to use devtree from your device. Also you could unpack ramdisk, and check the init.*.rc scripts if they are ok(e.g. I mount system partion using p21, not sure if that's the same for defy, and staff like that).
Android 4.2.2 Jellybean for Defy and Defy+
Mirrors: http://www.uncledan.it/android-files/CM10.1/
Gapps: http://goo.im/gapps
Experimental builds with 3.0.8 kernel:
Not for daily usage!
Download Link: http://quarx2k.ru/cm10.1-nightly-defy+/!!!experimental!!!/
Works: SD-Card, Bluetooth, Torch, Leds, USB all modes, HW Video decoding, Sensors, FM-Radio (only seek stations+RDS), Sound (only speaker).
Not work: Headset, BT-headset, FM-Radio sound, Phone, GPS, Camera, FM-TX, WiFi.
Known problems: Low speed of USB Mass-storage, Display not always wake after sleep, Suspend not work correctly.
Builds on stable 2.6.32 kernel:
Download Link: http://quarx2k.ru/cm10.1-nightly-defy+/2.6.32/
Mirror: http://d-h.st/users/Quarx/?fld_id=14052#files
Problems/TODO:
1. BT-headset has problems.
2 .BT will not work, if FM is enabled.
3. Video recording is not good.
4. Memory leak after some days.
5. Delay on wakeup.
09.04.13: Suspend optimizations.
13.04.13: Fix BT, add Volume Rocker Wake Support and Expanded Desktop preference. 5Ghz WiFi (not tested)
15.04.13: Fix FM-Radio, Add pie controls, TWRP recovery..
11.05.13 Updated USB-Gadget to native for 4.x, fix mtp/ptp/storage/tethering. Removed usb.apk/usbd. Many minor fixes..
16.05.13 Very experimental build, contain a lot of updates from kernels 2.6.33 - 3.1. Increased performance, added swap. Memory management updated to 2.6.39(3.0) state. Some parts updated to 3.1. Blechd0se patches for interactive gov.
07.06.13 Fix 2g/3g data (thanks to Kayant for finding the right way to resolve problem). More safe mount options (should fix problems of random bootloops). Fix Google Messaging service (thanks to ccav2000)
16.06.13 Updated wifi driver & wpa_supplicant, fix bt-tether by @dh.harald. Improvement in interactive governor by @Blechd0se. Updated kernel with some patches from upstream.
09.07.13 Stability fixes. Updated bootmenu. This build not contain ZCache/Zram/Swap. Who want use ZRAM and other experimental features, can install @Blechd0se's kernel
F.A.Q
Coming from CM 10
Do we need to wipe data to update the CM10 build to CM10.1?
Edit: I will try it, btw. thanks Quarx for the awesome work
GUYS u must flash gapps , if u want to go past the setup during first boot
Fire Head said:
Do we need to wipe data to update the CM10 build to CM10.1?
Click to expand...
Click to collapse
Remember that it's not ready for daily use. Nearly everything doesn't work. You have to wipe everything in order to make it boot. And of course, flash gapps too.
how to get pass , the first boot setup ,
the gapps provided is too large for defy's data partition
so cant get specific needed files for setup , can any1 help ??
i still cant get pass the setup
Quarx, I recommend you to post this link to the OP:
FAQ thread for the new CM10.1!
http://forum.xda-developers.com/showthread.php?p=34616788
----
Guys, remember to hit the "newsworthy thread" button on the OP! The world needs to know this!
Okay, the excitement is understandable, but guys, can you keep this thread CLEAN? Express your gratitude with a donation and the Thanks button, not by flooding the thread with delighted squeals. It's development after all.
I hope (in vain though) that this will be the last offtopic post.
Trimis de pe ASUS Transformer Pad TF300T
So for me, after PIN input, it shows "Unfortunately, the process com.google.process.gapps has stopped" and then "Unfortunately, Setup Wizard has stopped" message... and it stays like that even after i press OK! I can access notification bar, but no start screen!
What to do?
Gafanhotz said:
You have to wipe everything in order to make it boot.
Click to expand...
Click to collapse
Not really, installed it over CM10 (with the new GApps) and deleted cache (and dalvik cache). It works
Fire Head said:
Not really, installed it over CM10 and delete cache (and dalvik cache). It works
Click to expand...
Click to collapse
He said on Facebook to wipe data in order to make it work without major problems.
bone101 said:
No Sdcard here
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
That should be in his to do list don't worry. This is something beyond imaginary what we are going to experience. So thank him for what we have. You know about him. He will surely make it stable.
Sent from my MB526 using xda premium
Gafanhotz said:
Quarx, I recommend you to post this link to the OP:
FAQ thread for the new CM10.1!
http://forum.xda-developers.com/showthread.php?p=34616788
----
Guys, remember to hit the "newsworthy thread" button on the OP! The world needs to know this!
Click to expand...
Click to collapse
Can't find that button..maybe it is not available in tapatalk but only in Web visualization?
Hope this thread will be cleaner than 4.1.2 one..guys for support please use faq thread!
System Wizard stopped fixed
After installing CM10.1 with gapps you can't bypass Setup Wizard stopped. How bypass this error: 1.wipe all data 2.install CM10.1 nightly 3.Wipe all data 4.boot in 4.2, it will boot without errors. 5.Install your needed google apps from market. Error caused by gapps (I think its because low space in ROM - installing CM10.1 without gapps i getted only about 15mb free), so if we want to use future ROMS (4.3 - CM11 or CM10.3) we need to resize SystemROM, to resize SROM - we need unlock bootloader, to bypass bl - TI Board Conf tool & 16MB.bin or some future way )
can i install for Defy green lans ??
slon11 said:
can i install for Defy green lans ??
Click to expand...
Click to collapse
Its for Defy and Defy +.
Since we have custom kernel, every build is for both phones, regardless the lenses
Sent from my Balls of Steel
Can someone make audiofix flashable from cwm as temporary solution ? Beside this rom speed is very good
Audio fix CWM flashable ZIP
I made CWM flashable audio fix.
turffe said:
I made CWM flashable audio fix.
Click to expand...
Click to collapse
Yes thanks a lot,but how to mount sdcard to save download from Tapatalk ?
sebx_g1 said:
Yes thanks a lot,but how to mount sdcard to save download from Tapatalk ?
Click to expand...
Click to collapse
SD is mounted, but android is not seeing it as mounted.
Nothing you can do about it..
Sent from my Balls of Steel
I've spent some time trying to tweak and tune a kernel for the Nook HD+ ovation device.
This is the result so far:
http://www.mediafire.com/download/wwjq7jp1ppbohqb/cm-10.1.3-ovation_OC6.zip
It's packaged as a complete rom to avoid kernel module difficulties. The rom is completely stock minus the boot animation, kernel and kernel modules. Thanks to everyone who has made this possible.
Both the kernel and PVR module have been compiled with linaro.
The kernel has numerous performance and stability enhancements over any other kernel to date.
Great Work. Thank you very much!
Hi Jon, I upgraded to OC6 but it doesn't works so good like OC4? ( i did a clean install) i added last_kmsg may you can find why my device start rebooting again :<
wahidx said:
Hi Jon, I upgraded to OC6 but it doesn't works so good like OC4? ( i did a clean install) i added last_kmsg may you can find why my device start rebooting again :<
Click to expand...
Click to collapse
I appreciate the last_kmsg. I apologize for using everyone as beta testers, but this demonstrates why it is a good idea- because I have been running OC5 for a few days without a single hiccup at all. I am actually surprised OC4 did so well for you. OC4 was also the first version to sport a new pvr module.
One thing I had been noticing before being able to compile my own pvr was that I could have one kernel play well with the stock pvr, and I could have a kernel right after that not play well with the pvr at all. This was my major motivation to be able to compile my own pvr so that it could match kernel space every time.
Ok, with that said, I compiled the pvr against OC4, and didn't bother updating it against any subsequent kernels. I probably should have known better, but it was working well enough for me.
Your error looks suspiciously like a missmatch between the pvr and kernel space. So if you want to try this update:
http://www.mediafire.com/download/qyaqt9mukrqbdvj/cm-10.1.3-ovation_OC7.zip
and let me know if it works any better. I made sure to compile the pvr to specifically match the kernel.
Also, when I compiled the pvr before, I used PLATFORM_VERSION=4.1. I used this as an excuse to try
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- BUILD=release TARGET_SGX=544sc PLATFORM_VERSION=4.2.2
I don't know if it makes a difference or not.
Another thing I noticed you have slightly different hardware than I do. You have elpida ram versus samsung which is what I have.
I modified samsung ram timings to be slightly faster, but the other ram types were left at stock speeds. I may eventually try to clock the elpida ram the same as I have done with samsung, that may or may not make a difference. This may affect pvr performance as well. (It seems your pvr was a little slow bringing up power a few times). Then again, it could be my pvr source (although it works flawless for me, it may be hardware differences- I dunno.
thx for fast replay man,
i will try this release and give you feedbacks.
i have the bad feeling that something is wrong with my hardware. can be the only explanation, why my device reboot so often with CM10.2, CM11 and your OC6 release :/
//EDIT
actually i had just 1 reboot after some hour OC6 using, i will try OC6 for the next 2-3 days, maybe it was just a bad accident. after that i will try your OC7
regards
//EDIT #2
OC6 Test
after 2 days more, just 2 freez-->reboots (check last_kmsg) but still better than CM 10.2 and 11 on my device
Jon Lee said:
I've spent some time trying to tweak and tune a kernel for the Nook HD+ ovation device.
This is the result so far:
http://www.mediafire.com/download/wwjq7jp1ppbohqb/cm-10.1.3-ovation_OC6.zip
<snip>
The kernel has numerous performance and stability enhancements over any other kernel to date.
Click to expand...
Click to collapse
Hi Jon:
Hey, since we're asking for the moon, and since you're making THE oc kernel, any chance you can implement f2fs? I've got a Gal Tab 2 and an xda developer over there has a page about what he's done to get f2fs to work. Mostly it seems to require a .101 kernel. And he was kind to update TWRP so it would support f2fs. (I think to keep it from automatically formatting in ext4.) And he even wrote some zips to format /data, /system and /cache to f2fs.
My Tab 2 doesn't benchmark any faster but it sure is faster with f2fs. I image the HD+ would be faster too.
I'm new to flashing the Nook HD+. I was previously using the SDcard booting option for CM 10.1, but I would really like to get Nook off of this completely. Where do I start? I downloaded the ROM, and I have a boot IMG from another ROM on an SD card that takes me to recovery. Where do I put this ROM and how do I overwrite the actual Nook ROM?
install fails using verygreens internal recovery. is there a trick to installing this?
So I was able to flash the ROM, but I cannot upgrade. Everytime it tries to upgrade to 10.2 it reboots, I see the Nook logo, and then I get a Nook error screen. Does that mean I don't have the right CWM installed? If that's the case, how do I install the correct CWM?
SynGamer said:
So I was able to flash the ROM, but I cannot upgrade. Everytime it tries to upgrade to 10.2 it reboots, I see the Nook logo, and then I get a Nook error screen. Does that mean I don't have the right CWM installed? If that's the case, how do I install the correct CWM?
Click to expand...
Click to collapse
Yes, that means you still have stock recovery installed. You need to go to my HD/HD+ CWM thread linked in my signature and download and install the 6036 CWM from item 5 there.
Edit: but you know if you upgrade to CM10.2 you lose this kernel, right?
Sent from my BN NookHD+ using XDA Premium HD app
---------- Post added at 04:42 PM ---------- Previous post was at 04:41 PM ----------
smatticus said:
install fails using verygreens internal recovery. is there a trick to installing this?
Click to expand...
Click to collapse
It depends on which verygreen internal recovery you are using. You need to have version 6036 or older to flash it. You can get one per my previous post.
Sent from my BN NookHD+ using XDA Premium HD app
Great Work! I used OC7, it now worked on 1620Mhz and I feel faster. Is it possible to run on some higher frequency like 1800Mhz?
i6941 said:
Great Work! I used OC7, it now worked on 1620Mhz and I feel faster. Is it possible to run on some higher frequency like 1800Mhz?
Click to expand...
Click to collapse
Does this work for CM11?
andtron said:
Does this work for CM11?
Click to expand...
Click to collapse
I think the answer is no, when you flash cm11 the OC kernel will be overwrite. But I didn't try this.
As the thread title indicates, this kernel is only for 10.1.3.
it says there is a new update from the option -- about menu...should I?
Jon Lee said:
http://www.mediafire.com/download/qyaqt9mukrqbdvj/cm-10.1.3-ovation_OC7.zip
Click to expand...
Click to collapse
I couldn't find a tabletUI patch to match the final cm10.1.3 stable so here's one for anyone else downgrading like me.
Here's another experimental kernel update.
http://www.mediafire.com/download/1lkesmn6si6hd1e/ovation-kernel-cm10.1.3_v5.zip
I'm using it on OC7 pvr without issue (?).
1) reduced elpida and hynix ram timings.
2) updated vivante gc320 gcx 2d composition drivers to gitorious.org/gcx staging/alexei-dev. These are significantly different from original. (FWIW Staging/master branch threw memory map bverror 2 logs, but otherwise worked fine).
3) reduced dsp carveout memory. Increased system memory.
If needed, here is just the plain kernel for OC7, should anyone wish to revert back to that for any reason. (So as to not have to flash the entire ROM).
http://www.mediafire.com/download/z4r59n8dasxgz93/ovation-kernel-cm10.1.3_v4.zip
Kernel source for OC7
http://www.mediafire.com/download/6rngvee6x471cc3/android_kernel_bn_omap-cm-10.1_v3.tar.gz
So oc7 has been very unstable for me. I started with a completely clean slate, but it's frequently rebooting and not waking up from sleep. I may remember having these same problems when I was regularly using cm10.1 last year.
I've gone back to cm10.2.1. You should consider developing your kernel for that one.
Ya'know, I make these for me first and foremost. They reflect what I'm working on, trying to fix or improve the performance of my device.
Each one is different, some have worked better than others, but I notice an overall improvement from the original kernel. It is substantially different than any other nook kernel out there and works the best for me.
Here's the last. I think it works well. Made some additional changes to mmc/sdio to try and improve stability with wl12xx.
Source (which includes the vivante driver change from before):
http://www.mediafire.com/download/v4ihnr46eo9ap4d/android_kernel_bn_omap-cm-10.1_v4.tar.gz
Flashable kernel
http://www.mediafire.com/download/c9bsziswrf7y0e4/ovation-kernel-cm10.1.3_v6.zip
I like 10.3.1 but it has two downsides. 1) No automatic TRIM. 2) Unsafe manual TRIM because of Samsung MAG2GA EMMC bug.
Is it possible to implement the workaround used for 10.2.1 and later? Then manual TRIM by using console "fstrim" should be safe.
http://wiki.cyanogenmod.org/w/EMMC_Bugs
I assume the source for the 10.2.1 kernel would have the ported patch.
The purpose of this kernel is to provide the new features of the community to an older version of android.
To see this old version of android in its maximum splendor, trust on me, its better use kk on your smartphone than another version of android
FEATURES
for now (i am working on add some features but something gone wrong, and i think re-made everything, so keep calm)
-Fix wifi issue on dual sim version thanks to @kaminari
-Reclaim ram from loggers
-Fixed some memory leaks
-Xperience Governor WIP
-OC/UC Bus
-OC/UC GPU 600 mhz-100mhz
-OC/UC/UV CPU up to 1.6ghz-96mhz
-Compiled With Sabermod 4.7
-Fix Screen Flickering and added ULPS
Click to expand...
Click to collapse
INSTALLATION
-Install a CM-AOSP KK rom (no works on GPE and Stock)
-Flash via TWRP or CWM.
-Enjoy
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------
| If something gone wrong.... you can follow a video tutorial from How-To Basic in YT to fix your device |
| Nah just a joke, give me a logs to see what can i do for you |
--------------------------------------------------------------------------------------------------------------------------------
DOWNLOADS
-----LINK----
FOLDER ON DRIVE
https://drive.google.com/folderview?id=0Bzhj4Q-XtM6RMkJjM19uT3hvQmc
Click to expand...
Click to collapse
BUGS
None for now
Click to expand...
Click to collapse
SOURCES
https://github.com/STR4NG3R/android_kernel_motorola_msm8226-1
Click to expand...
Click to collapse
Thanks to...
@hurtsky @BryanByteZ @TeamMex @h2o64 @kaminari @Slate21&MOTOG
-And all the real developers in this community.
Recomendations for best perfomance:
ROMS:
https://forum.xda-developers.com/moto-g/development/rom-cyanogenmod-11-4-4-kernel-fixed-t3431146
https://forum.xda-developers.com/moto-g/development/rom-speedmod-slimkat-based-lollipop-t3430480
TIPS:
Since the moto g have a partition thats isnt used for nothing(/cache partittion 600mb), , you can made a swapp file into it (with the apps ram expander from google play).
Click to expand...
Click to collapse
Wifi issue
Very nice Kernel. Better than others in all respect but one. Wifi cannot be turned on. I tried wiping cache, copying CM11 wifi module, persistence, etc... None worked. Any idea?
XT1033 dual sim here. Your kernel did fix the flickering issue and stopped random rebooting. But I am reluctant to use it due to the lack of wifi.
stonelight said:
Very nice Kernel. Better than others in all respect but one. Wifi cannot be turned on. I tried wiping cache, copying CM11 wifi module, persistence, etc... None worked. Any idea?
XT1033 dual sim here. Your kernel did fix the flickering issue and stopped random rebooting. But I am reluctant to use it due to the lack of wifi.
Click to expand...
Click to collapse
So weird ://// i dont know why
Is this rom based on Render? I checked the Render kernel website http://forum.xda-developers.com/showthread.php?t=2724016 and people were complaining about wifi not enabled on KK 4.4.4 and XT1033, which is exactly my phone. Unforetunately Render stopped developping in 2014.
Now I have an ugly workaround. Two kernels work to some extent:
Render or Culcalkin: I flash boot with pre_render_boot.img, all good except wifi.
Pink: I flash recovery with pre_pink_boot.img, has wifi, but suffers from random reboot, not able to wake up sometimes, and flickering screen at boot up.
So most of time I use boot image into Culcalkin. When I really need wifi, I reboot into recovery which is indeed pink kernel.
STR4NG3R-GUY said:
So weird ://// i dont know why
Click to expand...
Click to collapse
Does it work on gpe 5.1 bootloader?
stonelight said:
Is this rom based on Render? I checked the Render kernel website http://forum.xda-developers.com/showthread.php?t=2724016 and people were complaining about wifi not enabled on KK 4.4.4 and XT1033, which is exactly my phone. Unforetunately Render stopped developping in 2014.
Now I have an ugly workaround. Two kernels work to some extent:
Render or Culcalkin: I flash boot with pre_render_boot.img, all good except wifi.
Pink: I flash recovery with pre_pink_boot.img, has wifi, but suffers from random reboot, not able to wake up sometimes, and flickering screen at boot up.
So most of time I use boot image into Culcalkin. When I really need wifi, I reboot into recovery which is indeed pink kernel.
Click to expand...
Click to collapse
maybe are based in the same sources, tell me with which kernel's you dont have thats issues to make a EXP build for you
XMoDuLeSx said:
Does it work on gpe 5.1 bootloader?
Click to expand...
Click to collapse
yes it does.
im dead right now, never drink a lot X_X
I tried too many kernels and forgot where I got that boot image . The ROM that I used is http://forum.xda-developers.com/moto-g/development/4-4-4-rom-t2826944 and its buildin kernel works with wifi (but with the flickering issue etc.). And somehow I have a boot image called pre_pink_boot.img which also works with wifi.
Your kernel is the only CM11 kernel that does not have the flickering issue on my phone. All others suffer from a moving flickering line at bootup, until I turn off screen and turn it back on again.
I heard that CM12 and above does not have those issues but I like the compactness of CM11. And Xposed is much easier on CM11.
STR4NG3R-GUY said:
maybe are based in the same sources, tell me with which kernel's you dont have thats issues to make a EXP build for you
yes it does.
im dead right now, never drink a lot X_X
Click to expand...
Click to collapse
Next update will be in december i need to dedicate all my time to my college, i learn how to add a lot of features so its a promise... Next version version will be really featured
STR4NG3R-GUY said:
So weird ://// i dont know why
Click to expand...
Click to collapse
You need to put this in your Makefile:
Code:
LDFLAGS_MODULE = --strip-debug
Otherwise the wi-fi module will be over 30 MiB in size and it'll definitely not load (the proper size for the module is no more than 4 MiB). Both your defconfig and updater-script are fine, no need to change anything inside them.
*MiB: mebibyte or binary megabyte (1024² bytes).
Edit: This line is already present in the Makefile, but it's empty.
Code:
LDFLAGS_MODULE =
You need only replace this line with mine.
wifi issue
Kamin4ri, thanks. do you have a compiled working CM11 kernel that is stable and with WIFI? Mine suffers from random reboot on XT1033.
Kamin4ri said:
You need to put this in your Makefile:
Code:
LDFLAGS_MODULE = --strip-debug
Otherwise the wi-fi module will be over 30 MiB in size and it'll definitely not load (the proper size for the module is no more than 4 MiB). Both your defconfig and updater-script are fine, no need to change anything inside them.
*MiB: mebibyte or binary megabyte (1024² bytes).
Edit: This line is already present in the Makefile, but it's empty.
Code:
LDFLAGS_MODULE =
You need only replace this line with mine.
Click to expand...
Click to collapse
Updated
what is the decryption key?
stonelight said:
what is the decryption key?
Click to expand...
Click to collapse
Moved to G-Drive
Thank you!