Does anyone know if Ant+ support is working in the CM12.x builds yet? Actually any info regarding this would be appreciated.
Also, should Ant+ be working in any of the stock based builds such as http://forum.xda-developers.com/xpe...m-existenz-ultimate-1-0-5-light-dark-t2835196 ?
Again, not a lot of info out there and it's hard to search for as the + is always getting dropped.
Which ANT+ chip is in the Z2?
http://forum.xda-developers.com/hardware-hacking/hardware/ref-devices-ant-hardware-t2879990
This is a good question.
It's a Qualcomm 801 SoC. https://www.qualcomm.com/products/snapdragon/processors/801
Is that helpful? I dunno.
Post #2 in the thread I linked to has some tips for knowing what hardware is used. If you are running a stock ROM (or any with ANT+) you can follow step number 3, simply running the ANT Support Checker app.
iRant said:
Post #2 in the thread I linked to has some tips for knowing what hardware is used. If you are running a stock ROM (or any with ANT+) you can follow step number 3, simply running the ANT Support Checker app.
Click to expand...
Click to collapse
Yes, I had a go at that today. I am running a Paranoid ROM based on CM11 I think. I can't even get the checker app to run, just immediately crashes.
I am going to try to move to the ROM I cited in OP, which I think is based on stock. It *should* support ANT+. No confirmation yet though.
Related
CM 7.2.0 Android 2.3.7:
CyanogenMod 7.2.0 port for FIH FM6 varaints.
Working:
USB
Sensors(partially)
GPS
Audio
Camera(partialy)
Wifi
OpenGL/graphics
Video Playback
Bluetooth
RIL
Bugs:
1) Front Camera is not working
2} Main Camera Zoom is not working for higher resolutions.Works upto some extent for QCIF
3)Portrait orientation is not proper.Some apps run upside down
4)Device suffers from very rare reboot due to kernel panic
Download Link:
ROM:
Code:
http://goo.im/devs/mb-14/viewpad7/cm-7-viewpad7.zip
GAPPS Package:
Code:
http://goo.im/gapps/gapps-gb-20110828-signed.zip
Installation:
Boot into CWM 5.0.2.8 recovery
Wipe DATA and Dalvik Cache
Flash ROM
Flash GAPPS package
For DEVS:
Here is my device config:
Code:
https://github.com/mb-14/android_device_viewsonic_viewpad7
Any help will be appreciated.
BUG REPORTING:
You must follow these instructions exactly, or I will ignore your requests. Provide the following information:
Report any customizations you have made to the ROM (themes, system apps, etc.)
Describe the problem clearly, including steps on how I can reproduce the issue.
Provide a logcat from your system taken just after the issue has occurred. To take a logcat, you enter this command from your PC: adb shell logcat -d >c:\logcat.txt.
Alternatively, if I ask for a radio logcat, this is the command: adb shell logcat -b radio -d >c:\logcat-radio.txt. Copy and paste this log to pastebin.com, and provide the link.
Send all this information to my email ID:[email protected] with subject as CMBUG
Credits:
CyanogenMod Team for their awesome ROM.
Goo-inside Team for providing their build server
Please donate to these people
Plea for help:
This project would not have been possible without the help of Goo-inside Me Team.
Now they require financial help for upgrading their servers.Please donate to them!!!
For more info check out their website: http://goo.im/
I am eager to test this beta build, and in anything i can help you with... im using a viewpad 7
Happy to be a beta tester.
I will settle up a ubuntu system to follow you. Please let me know what I can do.
All non-working functions are related with kernel?
WOw!!! I'm waiting.
s2k7 said:
Happy to be a beta tester.
I will settle up a ubuntu system to follow you. Please let me know what I can do.
All non-working functions are related with kernel?
Click to expand...
Click to collapse
Non-working functions are due improper implementation of hardware drivers(working on it)
Right now ill be commiting changes to the device config but due to hardware limitations
it takes lot of time to compile a build.
If you have sufficient hardware resources(RAM,space,cores)
you can clone my repo ,download and build the Cyanogenmod source and test it on your phone
PM me for any queries
s2k7 said:
Happy to be a beta tester.
I will settle up a ubuntu system to follow you. Please let me know what I can do.
All non-working functions are related with kernel?
Click to expand...
Click to collapse
+1, same here, can help debug the issues and work with adb.
Maybe an Irc channel for quicker contact?
cant wait for this. very willing to test
slightly off topic from an android-noob: Why still Android 2.x.x?
Any hope of Android 4.x.x (ICS) in viewpad7?
Best regards
sirgawain123 said:
slightly off topic from an android-noob: Why still Android 2.x.x?
Any hope of Android 4.x.x (ICS) in viewpad7?
Best regards
Click to expand...
Click to collapse
I'm think cause 2.3 and 2.2 have most possibility to use in stable. Viewpad 7 is to old to play around. And if this device have rom that can use maximum hardware's can do and stable. I think maybe we can see Viewpad7's ICS ROM in real life.
Sorry for my weak english.
sirgawain123 said:
slightly off topic from an android-noob: Why still Android 2.x.x?
Any hope of Android 4.x.x (ICS) in viewpad7?
Best regards
Click to expand...
Click to collapse
Tnie device seems too weak for ics, its a single core 600mhz armv6 CPU.
ics think it wil work on oure device it`s been ported too the x8 to and that`s a arm v6 600 mhz to,
but im happy with 2.3.7
Well, as long as I get 7.1 I'm happy. I still think having it ported is one thing but having it work flawlessly for everyday use is another.
Is wifi working yet? I've seen some commits on github but haven't seen any updates to the update.zip file in the first post.
*edit* where is the update.zip, exactly? Can't seem to find it on the first post anymore
Also, the sensors readout for screen orientation should be somehow flipped or mangled, for by default the device seems to be in landscape mode and if turned to portrait, it flips upside down for me.
hi
really appreciate you looking into porting this to the viewpad/variants etc
hope it goes well, looking forward to a little added ooompf,
(though [ROM]EUViewpad7 v1.7b has been great too)
@googlehome how's the progress?
@anyone I'm a programmer but i'm new to this android build compilation etc. Could anyone point me to tutorial or manual on how to these and those? Thx.
Yes, viewpad 7 seems to weak for ICS... We didn't even get honeycomb (3.X)
Dear Santa...
I'll be happy just with 2.3 and using my front camera with skype or gtalk...
Happy Holidays
Thank for hardwork
Hi
I think Gingerbread is perhaps as far as this device will go - in terms of functionality and "useablilty" - sure I'm sure ICS will "go on" if attempted but i'm pretty sure will fail to be useful (and if someone proves me wrong then I still win as I'll use it)
anyway keep up the good work with this gingerbread attempt - I'm hoping it goes well
Any news for the new year?
This is a call out to all existing and future developers of Xperia MDPI Devices.
For about a month now there is an app called Update Me Smartphone, which basically gives OTA update functionality for our Custom Roms.
From 01/05/2012 the developer of this app has given it a very interesting feature. You can view all Roms compatible with the Update Me Smartphone application. Even though you get a list a bunch of irrelevant devices, I suppose if we all "help" him with our suggestions he can make an application that will be on par with the Rom Manager app for devices that are fully supported by CWM.
To make this as simple as possible....
User "A" wants to download a new Rom for his Xperia MDPI Device. He has already downloaded and flashed a custom kernel (whether this is a Stock Kernel, or a CM kernel), then proceeds to download the app, install it and browse any compatible Rom's with his device... From then on his device will stay updated, through the Update Me application providing OTA updates of the Rom he has installed. If he wished to download another rom (compatible with the kernel he has - there are 3 Different Kernels AFAIK: GB CM, ICS CM, GB-ICS Stock Sony Kernel) he will just proceed to download the latest version of the rom he has selected straight to his device. No need to download to your computer, then connect the device, then copy it, then flash it. If you have the compatible kernel already installed, then its easy as pie.
Please let me know of your thoughts on this...
Edit: Link to the application's thread http://forum.xda-developers.com/showthread.php?t=1590170
Edit 2: Apart from Rom's we can also implement various mods, tweaks, fixes, etc for our devices. Even though that would be extremely hard, due to the fact that all these files need to be stored in a direct download location like Dropbox, its is a viable option.
OMG I love the idea, that would be awesome!!
It's very interesting, thanks a lot for the info I will try it!
Some modification: In GB we have 3 different kernel (Stock Based, CM Based, MIUI Based [not released yet]). In ICS we don't have Stock based to Xperia MDPI, because Sony don't released yet the stock for us. So we have CM9 based, AOSP based (it's work with CM9 ROMs btw), and ported Stock based.
Some another notice: I saw a lot of thread (not only in this forum), but sooo many people trying to make ROMs. It's not a problem, but some guy don't know some full minimum things... So who will help this guys to add this app to their ROMs?
Are you using a different Kernel for the Sony ICS rom port? I mean the Ramdisk is the same size and you're using the same zImage from a stock GB rom correct?
Well nobody is forced to do this. All we have to do is provide the app developer a link with the update_me_check.xml so that he will sort of add a link for that in the application.
By the way, i now got my goo.im account, and this have own OTA app. I will try it, and I will report.
But I know, this is not only OTA app... Hmm... I need to think in it
So the only developer checking the thread is Expeacer?
Ok...
dumraden said:
So the only developer checking the thread is Expeacer?
Ok...
Click to expand...
Click to collapse
What makes you think like this?
Well, it's been a couple of days since I posted this, either people dont have an opinion of their own, or they don't care...
dumraden said:
Well, it's been a couple of days since I posted this, either people dont have an opinion of their own, or they don't care...
Click to expand...
Click to collapse
I also read quite a lot of topics, but I don't respond in every topic.
I'm not understanding how kernels and ROMs connect. Can someone give me some extra insight?
[Hardware] <-- Unique to every phone
--
[Kernel] <--- Tells the OS how to talk to the hardware
--
[ROM] <--- Slightly confused. Is the OS in the Read only Memory, or has this term changed its "street" meaning?
I understand that most ROMs (e.g. CM7 and CM9) include both the kernel and the ROM, but can you flash these separately too?
I have a 1.5 year old thunderbolt that's rooted, and has CM7 which is based on gingerbread. I believe HTC has also released the kernel as open source, which is probably the reason I have CM7
Anyway, I guess what I'm looking for is an answer/guide/forum that explains why I can't install newer versions of android onto the already working/open source kernel I'm already running. Is it accurate to view the kernel as all the phone's drivers, or just the CPU driver? If that statement is true, why can't I load ICS or Jelly Bean onto my already existing set of drivers?
I'm thinking about starting a Wiki on this if 1) it doesn't already exist, and 2) I can wrap my brain around it enough to share with others!
Thanks to anyone with a response!
shadowrelic said:
I'm not understanding how kernels and ROMs connect. Can someone give me some extra insight?
[Hardware] <-- Unique to every phone
--
[Kernel] <--- Tells the OS how to talk to the hardware
--
[ROM] <--- Slightly confused. Is the OS in the Read only Memory, or has this term changed its "street" meaning?
I understand that most ROMs (e.g. CM7 and CM9) include both the kernel and the ROM, but can you flash these separately too?
I have a 1.5 year old thunderbolt that's rooted, and has CM7 which is based on gingerbread. I believe HTC has also released the kernel as open source, which is probably the reason I have CM7
Anyway, I guess what I'm looking for is an answer/guide/forum that explains why I can't install newer versions of android onto the already working/open source kernel I'm already running. Is it accurate to view the kernel as all the phone's drivers, or just the CPU driver? If that statement is true, why can't I load ICS or Jelly Bean onto my already existing set of drivers?
I'm thinking about starting a Wiki on this if 1) it doesn't already exist, and 2) I can wrap my brain around it enough to share with others!
Thanks to anyone with a response!
Click to expand...
Click to collapse
You are correct about the ROM, but ROMs also include the kernel (if it didn't, or no kernel was flashed separately, the device would not boot). Yes, other kernels can be flashed on your existing ROM, but it's not necessarily going to be compatible.
Sort of, but there's a lot more than that. See here and here. Later versions of Android will require newer drivers,etc. which the existing kernel won't provide (they'll be outdated). Back porting and additional coding is theoretically possible, but insanely difficult (many times). Even after this some things may still not work.
Thanks for the insight, I was able to get a lot deeper into this with those links. For anyone else wandering down a similar path, you might as well stop now! Here are a few links:
http://forum.xda-developers.com/showthread.php?t=1039217&page=2#17
http://www.cs.uwc.ac.za/~mmotlhabi/avmk.pdf
http://www.iteachandroid.com/2012/01/what-is-firmware-rom-and-firmware.html
So, if anyone else is still listening, I do have two more questions:
Do any phones have truly open source drivers? (a.k.a. higher probability of allowing old hardware to work with new android OS)
Is there any way to determine which phones will be supported by the custom-ROM community early on? I know the Nexus line doesn't have vendor modified code, is that the direction which would have the highest probability to stay at top of the Custom ROM curve without upgrading devices every year?
Thanks again for any insight! I hope I'm posting this in a Newb-Friendly forum!
shadowrelic said:
Thanks for the insight, I was able to get a lot deeper into this with those links. For anyone else wandering down a similar path, you might as well stop now! Here are a few links:
http://forum.xda-developers.com/showthread.php?t=1039217&page=2#17
http://www.cs.uwc.ac.za/~mmotlhabi/avmk.pdf
http://www.iteachandroid.com/2012/01/what-is-firmware-rom-and-firmware.html
So, if anyone else is still listening, I do have two more questions:
Do any phones have truly open source drivers? (a.k.a. higher probability of allowing old hardware to work with new android OS)
Is there any way to determine which phones will be supported by the custom-ROM community early on? I know the Nexus line doesn't have vendor modified code, is that the direction which would have the highest probability to stay at top of the Custom ROM curve without upgrading devices every year?
Thanks again for any insight! I hope I'm posting this in a Newb-Friendly forum!
Click to expand...
Click to collapse
For both your questions, the Nexus-line devices would be the way to go. They usually have everything working on new Android versions the soonest, and Google always releases their code, etc.
Hi
i can use linux kernel (zimage) to update android kernel if yes ,how ?
thnx
palmbeach05 said:
CM dropped official support due to kernel stability issues. I remember we were discussing ROMs. 7.2 was, according to CM, the last stable version. Due to all the changes when everything became 4.0, the kernel became unstable on our device. Our devs have created a kernel that is stable enough for daily use, but not stable enough for an official CM. You do have CM9, 10, 10.1, 10.2, and 11 that are stable. CM12 needs work before being recommended for daily use.
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the information, glad to see that i can still get support for this device. :good:
I'm trying to get general information for the last 2 days, reading especially the Q&A and development sections in the forum . If i understood correct;
* There's a new kernel being developed named as [KERNEL] [3.1.10] as you mentioned in your post. This new kernel seems nearly perfect, it just has these 3 downsides regarding the given information on its own topic:
1) HDMI [post-poned] (Nvm, I don't need it)
2) Fingerprint ROM Libs+Framework [work in progress] (Nvm, I don't need it)
3) Flash [work in progress] (Camera flash? It would be nice, but still not mandatory for me)
So i thought i could try the newest unofficial CM releases based on this new kernel. I checked the most-used ones in the development section for CM11, CM10.1, CM10, CM9. But i learned a very disappointing thing in the posts. If it's true, although bluetooth is operable for data transfer, it is NOT working for voice, meaning that i won't be able to use it in my car. :crying:
Other negatives are not that important, but GSM calls over bluetooth is very necessary for me. Because it's a security issue, as most of all need to use our phones while driving! So i regrettably had to eliminate the CM Roms which use this new kernel for now!
I need a Rom that is stable enough and has a wide hardware support such as necessarily:
1) Calls over bluetooth
2) GPS
3) Wi-fi tethering (USB tethering is not important)
Plus; android version must be new enough to support some of the applications. I found out that i need at least CM10 (Android v4.1) for the applications that i need to install.
At the end i can summarize my choices as follows:
* CM7.2 based Roms: All of them seem very stable, but some of my applications doesn't work on Android 2.3, so negative.
* CM9 based Roms: New kernel or not, Android v4.0 is old for a few of my applications. So, negative.
* CM10 based Roms: "CM10 (JellyBean) for Atrix" from @epinter seems very appropriate for me. It doesn't use the new kernel and Android v4.1 is sufficient (recent enough) for my applications. POSITIVE
* CM10.1 based Roms: "CM 10.1(Android 4.2) for Atrix" from @epinter could be very good, but it uses the new kernel. So, negative.
* CM11 based Roms: "CM 11 ( Android 4.4.4 ) for Atrix (BigPart)" from @Zn7mkUKzN1r8aCIV would be perfect, but i think it also uses new kernel, as it's indicated that ".BT phone call" is NOT working. So, negative.
* CM12 based Roms: I saw the "Mokee For Atrix 4g (Android L 5.0.2) (preview)", but as you see, it's not an option for me yet. So, negative.
If i didn't misunderstood what i've read till now, the most appropriate Rom seems;
"CM10 (JellyBean) for Atrix, By epinter" for me.
Link: http://forum.xda-developers.com/showthread.php?t=1781970
I think it would be better for me to continue on its own Q&A thread, I don't want to ruin this CM7.2 thread anymore.
Please share your opinions, i really need your advises.
EDIT: Oopss, basic kernel on CM10 seems lacking HW acceleration. So, i can't play NFS Most Wanted, Dead Space, Max Payne etc. games properly, right? What about navigation apps like iGo, Sygic, etc?
EDIT: This post was originally in the "CM7 Q&A" section and moved here as a seperate thread. My aim is not to find the "Best Rom ever" etc., i just seek for a Rom that's similar to the current awesome CM7, which fits my needs. I think i could find the best title for this post.
I wanted to ask, witch Roms are stable and support all features of Kenzo.
It seems that in several Roms there are different Problems,
from wakelocks and Battery drain,
over Wifi Problems
to missing Fingerprint or VolTE support.
Is it a Problem with Android 6.0 or also with 5.1 based Roms?
This should be in the Questions & Answers section. However, I have official CM 13.0 and I haven't encountered any of the problems that you mentioned above. If you read instructions carefully and understand what you're doing, you won't have any trouble as long as the rom you are flashing supports those features. If you head over to the Android Development section, you can see the features that each rom does and doesn't support. If the OP says it is supported but you can't get it to work, then the problem comes from your side. Before flashing make sure you have read and understood the required steps and have taken all the necessary precautions to avoid ending up with a "bricked" device. Let me know if you have any trouble.
jimakos98 said:
This should be in the Questions & Answers section. However, I have official CM 13.0 and I haven't encountered any of the problems that you mentioned above. If you read instructions carefully and understand what you're doing, you won't have any trouble as long as the rom you are flashing supports those features. If you head over to the Android Development section, you can see the features that each rom does and doesn't support. If the OP says it is supported but you can't get it to work, then the problem comes from your side. Before flashing make sure you have read and understood the required steps and have taken all the necessary precautions to avoid ending up with a "bricked" device. Let me know if you have any trouble.
Click to expand...
Click to collapse
Thanks for your reply,
yes i know what im doing (had Nexus 4 and flashed it more than a hundred times).
I normally check first post (+ following from OP) and the last sites of the Thread to see if there are bugs or not (cause "no bugs" in OP-Thread is not always correct).
But if CM13 is, so far, bug free and full featured (fingerprint and so on) than i will give it a try.
DarkAlucard said:
Thanks for your reply,
yes i know what im doing (had Nexus 4 and flashed it more than a hundred times).
I normally check first post (+ following from OP) and the last sites of the Thread to see if there are bugs or not (cause "no bugs" in OP-Thread is not always correct).
But if CM13 is, so far, bug free and full featured (fingerprint and so on) than i will give it a try.
Click to expand...
Click to collapse
It is. I've been using it for almost 1 month now, and I can say it's probably the most stable and complete rom for me. I also flashed the CM 13.0 supported firmware along with Radon Kernel and the device is blazing fast. As for the battery, I can get 1 week+ with minimal usage, and about 2-3 days with heavy usage which is pretty impressive for a hexa-core device with a 1080p screen.
jimakos98 said:
It is. I've been using it for almost 1 month now, and I can say it's probably the most stable and complete rom for me. I also flashed the CM 13.0 supported firmware along with Radon Kernel and the device is blazing fast. As for the battery, I can get 1 week+ with minimal usage, and about 2-3 days with heavy usage which is pretty impressive for a hexa-core device with a 1080p screen.
Click to expand...
Click to collapse
I was wondering about this "firmware" thing, never had to upgrade any software. Normaly just flash the Rom.
I was also wondering what's the difference to the unofficial CM13
DarkAlucard said:
I was wondering about this "firmware" thing, never had to upgrade any software. Normaly just flash the Rom.
I was also wondering what's the difference to the unofficial CM13
Click to expand...
Click to collapse
Well, if you are going to flash this rom you are going to have to flash the appropriate firmware too, since CM is based on it. If you flash the rom without flashing the firmware, you might end up with missing options in settings (I tried this and the "fingerprints" tab was missing). As soon as I flashed the firmware everything got fixed. Also, an official rom means that it is developed by a member or a group of members that have created the original project, while unofficial roms can be built by anyone. For example I can take a CM build and customize it the way i want and then release it to the public. This makes it an unofficial rom, since I'm not a member of the CM development team. But if a rom or an update releases on the CM website, then it is considered to be official.
By the way about the VoLTE support, quoting from OP Q&A:
Q) Is VoLTE supported? (Also useful if you have GApps related problems).
A) No. We use all proprietary blobs from MIUI Marshmallow alpha 'leaked' builds and those builds itself do not have it working. So we'll have to wait until Xiaomi fixes it in their marshmallow builds in future. Also we can't fallback to old LP radio blobs/libs and are not suited with current setup. #blamexiaomi
Click to expand...
Click to collapse
I guess you'll have to wait for Xiaomi to release a stable working MM build if you want voLTE support. :/