[Tutorial] Get Hardware info from your Atrix to help developers - Atrix 4G Q&A, Help & Troubleshooting

Hello folks! how are you doing?
Since we've seen Alpha kernel is still an alpha and we need to provide developers with every detail of our device we can.
I've decided to search through threads and get some commands from there to gather the information required:
You can gather these data by downloading Terminal Emulator from the market or by properly installing Google SDK and doing an adb shell then running the commands.
If commands do not seem to work at first glance, please reboot the phone then try again running the commands below.
Edit 1:
For all the people having problems not mentioned on the bug list, please report the problems in this spreadsheet
https://docs.google.com/spreadsheet/ccc?key=0AkQTVc3TvAUxdFNBOWFFRzNneWRHcW56MEtLVGJqdVE#gid=0
There are several sheets to fill with the mentioned problems
Edit 2:
For all users who might have problem gathering Tegra Revision, Speedo ID, CPU Process, Core Process; please install leaked rom / AtrICS, reboot and try searching again.
Else; please send me the dmesg command output via PM and I'll upload the results.
Please note that I'll discard dmesg from kernels that are not the leaked and/or 3.1
---
Identify Memory type:
Grab a terminal then run after a reboot
Code:
su -
dmesg | grep LPDDR2
Types of Memory
LPDDR2 MR5: 0x0003 (0x0303) = Elpida (Manufactuer)
LPDDR2 MR6: 0x0000 (0x0000) \
LPDDR2 MR7: 0x0000 (0x0000) / = 50nm
LPDDR2 MR8: 0x0054 (0x5454) = 1GB
LPDDR2 MR5: 0x0003 (0x0303) = Elpida (Manufactuer)
LPDDR2 MR6: 0x0001 (0x0101)\
LPDDR2 MR7: 0x0000 (0x0000)/ = 40nm
LPDDR2 MR8: 0x0054 (0x5454) = 1GB
LPDDR2 MR5: 0x0006 (0x0606) = Hynix (Manufacuter)
LPDDR2 MR6: 0x0000 (0x0000)\
LPDDR2 MR7: 0x0000 (0x0000)/ = 54nm (Note that this is still 54nm for MR7 = 0x0001 (0x0101))
LPDDR2 MR8: 0x0054 (0x5454) = 1GB
---
Identify which Panel Type do we have:
After a fresh reboot
Grab a terminal
Code:
su -
dmesg | grep atag
or
Code:
su -
dmesg | grep panel
Examples:
Code:
dmesg | grep atag
mot_parse_atag_motorola: panel type: 0x80000740
or
Code:
dmesg | grep panel
<6>[ 0.000000] parse_tag_motorola: panel_size: 0x740
---
Identify Tegra Revision:
Code:
su -
dmesg | grep Tegra
then search for something similar to
Code:
"Tegra Revision: AXX prime"
---
Well, let's see if we can help Atrix Kernel Team to improve the kernel with this useful information
Also, if anybody would like to contribute showing how to gather more data; that'd be awesome and I'll edit this post
Thanks guys, have a good day!

You are the man!!!....good work my friend...:good:

Thanks for this.

Thanks
This is super helpful. Now if I can just get my post count up high enough to post to dev forums....

Types of Memory
LPDDR2 MR5: 0x0003 (0x0303) = Elpida (Manufactuer)
LPDDR2 MR6: 0x0000 (0x0000) \
LPDDR2 MR7: 0x0000 (0x0000) / = 50nm
LPDDR2 MR8: 0x0054 (0x5454) = 1GB
Identify which Panel Type do we have:
dmesg | grep panel
<6>[ 0.000000] parse_tag_motorola: panel_size: 0x740
However, using command: "dmesg | grep Tegra" doesnt give me anything close to any revision information.

Seems like you ran dmesg a little too late. You need to run it as soon as possible upon bootup.

ravilov said:
Seems like you ran dmesg a little too late. You need to run it as soon as possible upon bootup.
Click to expand...
Click to collapse
Is it supposed to be a capital T in tegra? I rebooted several times and get the same stuff every time
I tried dmesg | grep revision
and got this:
CPU: ARMv7 Processor [411fc090] revision 0 (ARMv7), cr=10c53c7d.

vintage47 said:
Is it supposed to be a capital T in tegra? I rebooted several times and get the same stuff every time
Click to expand...
Click to collapse
No idea, but you can use grep -i Tegra, that should make capitalization irrelevant.

Solved, I was looking on dmesg from old kernel
--------------------------------------------------------------------------------------------------------------------------
Hello,
how I find the Tegra Revision, Speedo ID, CPU Process, Core Process that request Kristianp in my dmesg? I am stupid or it show diferent?
best regards,
Ferenc.

I cant find the tegra revision either. I can see the first thing in the log, but not the tegra revision.

Do after a fresh reboot in leaked kernel and Rom ( 10.1 epinter is mine)

Reboot when SD Card is present
Dear JhonnyX:
As I cannot write in the Google Docs Spreadsheet, please find the information from my Atrix Below. The Bug is the reboot when entering deep sleep with SD card inserted.
Sorry but I could not find my Atrix Revision on the early dmesg.
Best regards
Javier

ingelectronico said:
Dear JhonnyX:
As I cannot write in the Google Docs Spreadsheet, please find the information from my Atrix Below. The Bug is the reboot when entering deep sleep with SD card inserted.
Sorry but I could not find my Atrix Revision on the early dmesg.
Best regards
Javier
Click to expand...
Click to collapse
PM'ed you regarding the missing info
Also, users who might have spreadsheet access problem, please let me know via PM.

new fields
I want to add my info on the modem drops spreadsheet.
How do I find what values my phone has for these fields?
Speedo ID
CPU Process
Core Process
CPU governor

Connect the phone to usb and activate adb. Reboot. As soon as finished reboot, use adb shell and type dmesg > /mnt/sdcard/dmesg.txt
Now search that file.
This has been answered many tines before.
Next time use search
Enviado desde mi MB860 usando Tapatalk 2

Related

[KERNEL] Bricked-Kernel Grouper/Tilapia

Welcome to the most customizable N7 kernel on xda
Bricked-Kernel Nexus 7 (grouper)
Replaced NVIDIA's strange hotplug manager with my own: tegra_mpdecision​
Features:
Based upon Googles tegra3 source
Fixed section mismatches
Various other fixes (look @ github)
Compiled with gcc4.7.2 toolchain (linaro 09.12)
Replaced NVIDIAs hotplug manager with tegra_mpdecision (better battery life + performance)
Extensive sysfs interface for mpdecision with all the tuneables you want
Highly modified ondemand governor for tegra3 & mpdecision (this is the only recommended governor atm)
Fixed usage of 51Mhz clock
GPU OC (416/484/520Mhz)
Truly variant free CPU OC for all devices (51 - 1600Mhz)
Fixed max cpufreq resets throughout the kernel
All cores now use the max frequency (before: only in singlecore, otherwise -100Mhz)
Undervolting (faux123)
Default clocks: 102min & 1300max (+100Mhz overclocked) & 475 Maxscroff
earlysuspend/lateresume for ondemand including special screen off settings to save power
Aroma Installer by amarullz
cmdline interface for cpu min/max/maxscroff/gpuoc/scheduler/governor
---Just flash the kernel with your desired settings, no more need for oc apps. Reflash if you want to change sth. It's that easy!
FSync Control by Ezekeel
export t3 variant to debugfs by faux123 (adb shell cat /sys/kernel/debug/t3_variant)
lowered panel min brightness to 8
ZRAM
enabled NFSv3&4
Check the compare links for the rest ​
Where is tha Changelog???
There will be no more changelogs.
Instead the download pages were outfitted with compare links to github for each download.​
How to install?
Flash through recovery. #done.​
Where to complain about errors/bugs?
Please use the Issuetracker for bugs/errors/feature wishes!
Issuetracker @ https://code.google.com/p/bricked/issues/entry
[email protected]
IRC Chat: Freenode IRC #bricked​
Download:
No Guarantees! If it kills your grandmother or your device, I am NOT responsible! If you understand this:
(If you download, please hit Thanks below my post! Thank you!)
>>> DOWNLOAD <<<​
Donor List:​
> Hall of fame <
With special thanks to all N7 piggy bank donors!
Thank you very much!​
Source:
​
Benchmark:
Knowledge base:
What is tegra_mpdecision?
100% kernel based multi core decision! (should cpu1/2/3 be online or not, do we need the low-power/ninja core now?)
This replaces the stock nvidia hotplug solution.
Check /sys/kernel/tegra_mpdecision/conf/ for the configuration.
startdelay = time until mpdecision starts doing it's magic (20000)
delay = time between checks (130)
pause = if something else plugs in the cpu, fall asleep for 10000ms (10 secs)
scroff_single_core = Force low-power mode if screen is off (1)
enabled = enable(1) or disable(0) mpdecision. This does not affect scroff_single_core!
min_cpus = min cpus to be online, cannot be < 1. Default: 1
max_cpus = max cpus to be online, cannot be > 4. (if you set it to 2 and min_cpus to 1 you will basically have a dualcore) Default: 4
idle_freq = a value against that will be checked if a core +/- is requested. (475000)
lpcpu_up_hsyteresis = minimum number of requests that have to be send in order to switch to low-power mode (4)
lpcpu_down_hsyteresis = minimum number of requests that have to be send in order to switch to g-mode (quadcore-mode). Overridden by a requested freq that is higher than the max supported lp-mode frequency. (2)
If cpu0 is below that value and a core up of another cpu is requested, nothing will happen.
If any other cpu is above that value and a core down of that cpu is requested, nothing will happen. (otherwise it would now put down that cpu even though it is still working, which isn't what we want)
Hot plug thresholds (aka now it gets 'complicated')
This small formula calculates which value will be used: (number_of_cpus_online - 1) * 2
The result of this formula will be the nwns_threshold where a new cpu is hotplugged.
The result of this formula + 1 will be the nwns_threshold where a cpu is unplugged.
nwns_threshold_x = runqueue threshold, if this is reached cpuX will be hot/unplugged
twts_threshold_x = time threshold, this amount of time must have passed for the related action to be taken (hot/unplug)
Example:
One cpu is online.
(1 - 1) * 2 = 0 ergo:
nwns_threshold_0 = cpu1 will be hotplugged at this value
((1 - 1) * 2) + 1 = 1
nwns_threshold_1 = cpu0 will be unplugged at this value
This will regulate when we switch to lp-mode, effectively replacing the quadcore g-mode core with the ninja lp-mode core.
Two cpus are online.
(2 - 1) * 2 = 2 ergo:
nwns_threshold_2 = cpu2 will be hotplugged at this value
((2 - 1) * 2) + 1 = 3
nwns_threshold_3 = cpu1 will be unplugged at this value
etc...
(all times are in ms)
If you want to see the mpdecision magic happening:
Code:
adb shell
cat /proc/kmsg | grep 'MPDEC'
mpdecision's input event boost, aka project butter
This will boost your min cpu speed if you touch the screen or press a button and gives you full control.
In those events the min cpu freq will be risen to a predefined value (look below) on every online cpu. This boosts overall reaction times and smoothness a lot. (works similar to the qcom mpdecision binary)
Configuration files:
[email protected]:/sys/kernel/tegra_mpdecision/conf # ls
boost_enabled
boost_freqs
boost_time
All of them work like the usual sysfs files, except one special case:
boost_freqs will list all frequencies from cpu 0 to cpu x. Cpu 3 and any following cpu will share one frequency.
To change those frequencies echo the cpu number + the frequency in khz. To change the boost freq of cpu3 (and 4,5,6,7,8, etc) the echo would look as follows:
Code:
echo "3 1026000" > /sys/kernel/tegra_mpdecision/conf/boost_freqs
for cpu0:
Code:
echo "0 1026000" > /sys/kernel/tegra_mpdecision/conf/boost_freqs
Defaults:
Code:
cat /sys/kernel/tegra_mpdecision/conf/boost_freqs
910000
910000
760000
620000
Recommended governor?
Ondemand.​Why do I have no WLAN?
This kernel is too big for our boot.img with WLAN included into the kernel, so it is built as a module. That means it needs to be inserted into the kernel upon boot up, which needs to be automated for maximum comfort = userinit (init.d) support.
The zip adds init.d support to your ramdisk, if that fails for some reason the wlan module cannot be inserted.
if
Code:
adb shell lsmod
doesn't show this:
Code:
tun 14060 0 - Live 0x00000000
cifs 239646 0 - Live 0x00000000
bcmdhd 433083 0 - Live 0x00000000
Then init.d support is probably missing.
You can test it by going to /system/etc/init.d/ and executing 00wlan.
Code:
adb shell
su
. /system/etc/init.d/00wlan
Wait a few seconds and try to enable wifi and repeat the above lsmod command (should now show bcmdhd as live, you can execute 01cifs and 02tun too).
If WLAN now works, init.d support is missing.
You need to have busybox installed in order to be able to get init.d support going, this shouldn't be a problem for most people, since it is usually installed when rooting your phone anyway (and who does unlock but not root their phone? :/)
It does not matter if busybox is installed in /system/bin or /system/xbin, my script will detect the location upon flashing and patch the ramdisk accordingly.
If no busybox is found, the script will add init.d support to your ramdisk with the default location: /system/xbin/busybox. All you need to do is install busybox there and reboot your phone.
​
show-p1984 said:
Knowledge base:
(under construction)
tegra_mpdecision manual:
coming soon(tm)
Click to expand...
Click to collapse
looks great is this kernal compatible with cm10 based roms such as paranoid android
Flypants101010 said:
looks great is this kernal compatible with cm10 based roms such as paranoid android
Click to expand...
Click to collapse
Yes, ofc
Running cm10 nightlies myself.
show-p1984 said:
Yes, ofc
Running cm10 nightlies myself.
Click to expand...
Click to collapse
All AOSP roms work with Bricked
* Hello World *
What tweaks did you make to on-demand, if you don't mind me asking? The only thing I've noticed is that frequency switching seems to happen faster & more often.
Feel like flashing something tonight!
Sent from my Nexus 7 using xda premium
I tried flashing this a few times and it fails with each try.
Dabaum said:
What tweaks did you make to on-demand, if you don't mind me asking? The only thing I've noticed is that frequency switching seems to happen faster & more often.
Click to expand...
Click to collapse
I mostly adapted it to work with the lpcore while the screen is on and also with special power saving setting while the screen is off.
The 2 phase frequency was changed to accomplish that.
It also applies a powersave bias while screen is off.
Additionally I changed the settings to allow faster scaling with less load. (70% > freq incr)
Source is currently being uploaded, but since I kept the history intact it is taking ages. You can look it up there in more detail once the source is up
airmaxx23 said:
I tried flashing this a few times and it fails with each try.
Click to expand...
Click to collapse
With what message?
I guess because your recovery does not identify your device as 'grouper'.
show-p1984 said:
With what message?
I guess because your recovery does not identify your device as 'grouper'.
Click to expand...
Click to collapse
It just says failed, I've had no problems flashing anything else and I'm flashing mutilple times a day usually.
airmaxx23 said:
It just says failed, I've had no problems flashing anything else and I'm flashing mutilple times a day usually.
Click to expand...
Click to collapse
It most certainly does not say "failed" and nothing else. Look harder.
Using twrp recovery me and my beta testee had no problems at all.
show-p1984 said:
It most certainly does not say "failed" and nothing else. Look harder.
Using twrp recovery me and my beta testee had no problems at all.
Click to expand...
Click to collapse
It says "unable to open zip file. Error flashing zip."
show-p1984 said:
Yes, ofc
Running cm10 nightlies myself.
Click to expand...
Click to collapse
And just to be clear, with non-CM based ones as well? I'm running the 'Glazed' ROM....
airmaxx23 said:
It just says failed, I've had no problems flashing anything else and I'm flashing mutilple times a day usually.
Click to expand...
Click to collapse
Nothing wrong with the zipfile, maybe corrupted download? did you do md5 hash check before flash?
It's either your custom recovery or a corrupted download, period.
ps. Happy Flashing.
airmaxx23 said:
It says "unable to open zip file. Error flashing zip."
Click to expand...
Click to collapse
corrupt download? checked md5/sha1?
corrupt phone upload? checked md5/sha1?
friedsonjm said:
And just to be clear, with non-CM based ones as well? I'm running the 'Glazed' ROM....
Click to expand...
Click to collapse
As long as it is AOSP you should be fine.
But just try it and report back, then we are all a bit more enlightened
(Sorry, I can't possibly test all the ROMs out there ^^)
T-junk said:
Nothing wrong with the zipfile, maybe corrupted download? did you do md5 hash check before flash?
It's either your custom recovery or a corrupted download, period.
ps. Happy Flashing.
Click to expand...
Click to collapse
If I try downloading it directly to my tablet the resulting file is only 17.51K in size, downloading it with a computer takes care of the problem.
airmaxx23 said:
It says "unable to open zip file. Error flashing zip."
Click to expand...
Click to collapse
I get the same.
Sent from my Nexus 7 using xda premium
airmaxx23 said:
If I try downloading it directly to my tablet the resulting file is only 17.51K in size, downloading it with a computer takes care of the problem.
Click to expand...
Click to collapse
StrangerWeather said:
I get the same.
Click to expand...
Click to collapse
I guess same problem for you StangerWeather.
Try downloading on your pc, I will look into that webserver issue tomorrow. (or maybe it's a chrome issue? who knows ^^)

[Q] NextBook next8P12 rom 8inch display

Greetings, i have an nextbook - model in the back says netx8p12 and i tried to flash in several roms but all have the same problem. the image
dont fufill all the display.
The display is 8inch, in the website of the manufacter is 800x600 resolution so i downloaded the Oma_Odys_Loox_JB_4.1.1_v1.2.2a and flashed
with RKAndroid 1.29, all the files included except the kernel of the kernel_308_neo_x8_odys that belong to the next8p12.
I think i did ok but the problem is that image is like this images i uploaded
can anyone help me on this? like i´m really dumb person?
Big big thanks
joão
just found something.
i´ve downloaded one software from market, lcd resolution and it says:
width :464 dpi
density : 1
resolution : 464x320
Im with you
jfbbms said:
just found something.
i´ve downloaded one software from market, lcd resolution and it says:
width :464 dpi
density : 1
resolution : 464x320
Click to expand...
Click to collapse
If you make any progress let me know!
I bought one on Black Friday and haven't seen a successful flash yet...
Android System Info dump
Ok so let's get some information gathering rolling on this tablet.
Here's the dump:
Code:
OS
Browser UserAgent : Mozilla/5.0 (Linux; U; Android 4.0.4; en-us; Next8P12 Build/IMM76I) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Safari/534.30
Android ID : [Removed]
Uptime : 0 days, 3 hours, 9 minutes, 27 seconds
Uptime (without sleeps) : 0 days, 3 hours, 9 minutes, 27 seconds
Configuration
Font Scale : 1.15
Hard Keyboard Hidden : YES
Keyboard : NOKEYS
Keyboard Hidden : NO
Locale : en_US
MCC : 0
MNC : 0
Navigation : DPAD
Navigation hidden : NO
Orientation : PORTRAIT
Screen Height DP : 1018
Screen Width DP : 800
Smallest Screen Width DP : 600
Screen Layout :
LONG_NO
SIZE_LARGE
SIZE_NORMAL
SIZE_SMALL
Touchscreen : FINGER
UI Mode :
NIGHT_NO
TYPE_NORMAL
BuildInfos
Android version : 4.0.4
Release Codename : REL
API LEVEL : 15
CPU ABI : armeabi-v7a
Manufacturer : YIFANG
Bootloader : unknown
CPU ABI2 : armeabi
Hardware : amlogic
Radio : unknown
Board : M805MC
Brand : MID
Device : Next8P12
Display : V1.0.6.IMM76I.eng.root.20120917
Fingerprint : MID/NXM805MC/NXM805MC:4.0.4/IMM76I/eng.root.20120917.120120:user/release-keys
Host : midcs-desktop
ID : IMM76I
Model : Next8P12
Product : Next8P12
Tags : release-keys
Type : user
User : root
Battery
Charging in progress...
Level : 83 %
Technology : LiFe
Temperature : 30.0 ∞C (86.0∞F)
Voltage : 4007 mV
Memory
Download Cache Max: 128MB/ Free: 110MB
data Max: 440MB/ Free: 92.89MB
External storage: shared
External storage Max: -16384.00B/ Free: -16384.00B
External storage removable: false
External storage emulated: false
Total RAM: 413MB
Free RAM: 74.62MB
Threshold RAM: 41.50MB
Low Memory Killer Levels
FOREGROUND_APP:__ 17.00MB
VISIBLE_APP:_________ 22.50MB
SECONDARY_SERVER: 28.00MB
HIDDEN_APP:________ 36.00MB
CONTENT_PROVIDER: 41.50MB
EMPTY_APP:__________ 50.00MB
Telephony
Data Activity: DATA_ACTIVITY_NONE
Data State: DATA_DISCONNECTED
IMEI(or MEID): 510121043471011
IMEI/SoftVer: null
MSISDN: null
Registered MCC:
Registered MCC MNC:
Registered Operator Name:
Network Type: NETWORK_TYPE_UNKNOWN
Phone Type: PHONE_TYPE_NONE
SIM Country Code:
SIM MCC MNC:
SIM Operator Name:
SIM Serial Number: null
SIM State: SIM_STATE_UNKNOWN
Subscriber ID(IMSI): null
VoiceMail number: null
Roaming: false
No Cell detected
Networks
Background Data Usage: true
type mobile[UNKNOWN]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type WIFI[]
state CONNECTED/CONNECTED
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable true
type ethernet[]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type WIFI[]
state CONNECTED/CONNECTED
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable true
Wifi
State: WIFI_STATE_ENABLED
Current access point: SSID: [Removed], BSSID: [Removed], MAC: [Removed], Supplicant state: COMPLETED, RSSI: -19, Link speed: 65, Net ID: 0, Explicit connect: false
DHCP info: ipaddr 192.168.254.42 gateway 192.168.254.254 netmask 255.255.255.0 dns1 192.168.254.254 dns2 0.0.0.0 DHCP server 192.168.254.254 lease 86400 seconds
Last Scan:
0 SSID: [Removed], BSSID: [Removed], capabilities: [WPA2-PSK-CCMP][ESS], level: -42, frequency: 2412
Configured Networks:
0 ID: 0 SSID: "MCLAREN-DSL" BSSID: null PRIO: 1 KeyMgmt: WPA_PSK Protocols: WPA RSN AuthAlgorithms: PairwiseCiphers: TKIP CCMP GroupCiphers: WEP40 WEP104 TKIP CCMP PSK: * eap: phase2: identity: anonymous_identity: password: client_cert: private_key: ca_cert: IP assignment: DHCP Proxy settings: NONE LinkAddresses: [192.168.254.42/24,] Routes: [0.0.0.0/0 -> 192.168.254.254,] DnsAddresses: [192.168.254.254,]
CPU
Processor ARMv7 Processor rev 4 (v7l)
BogoMIPS 1011.71
Features swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer 0x41
CPU architecture 7
CPU variant 0x2
CPU part 0xc09
CPU revision 4
Hardware AMLOGIC MESON3 8726M SKT SH
Revision 0020
Serial 000000000000000c
Frequency range: 100.0 -> 1000.0MHz
Current Frequency: 650.0MHz
Frequency Stats (time):
Camera
As retreiving camera infos can give the impression that it is taking picture on some device, it is not enabled by default. If you wish to, go in settings menu.
Screen
Resolution: 600 x 764
Refresh Rate: 50.0
X factor for DIP: 0.75
Density: 120 dpi
Pixel per inch X: 160.0 dpi Y: 160.42105 dpi
OpenGL
As retreiving opengl infos can crash some device, it is not enabled by default. If you wish to, go in settings menu.
Sensors
MMA 3-axis Accelerometer: 0.2 mA by Freescale Semiconductor Inc.
Environment
Root Directory: /system
Data Directory: /data
Download Cache Directory: /cache
External Storage State: shared
External Storage Directory: /mnt/sdcard
Medias Directories
Alarms: /mnt/sdcard/Alarms
DCIM: /mnt/sdcard/DCIM
Downloads: /mnt/sdcard/Download
Movies: /mnt/sdcard/Movies
Music: /mnt/sdcard/Music
Notifications: /mnt/sdcard/Notifications
Pictures: /mnt/sdcard/Pictures
Podcasts: /mnt/sdcard/Podcasts
Ringtones: /mnt/sdcard/Ringtones
Features
android.hardware.wifi
android.hardware.location.network
android.hardware.location
android.hardware.touchscreen.multitouch
android.hardware.screen.landscape
android.hardware.screen.portrait
android.hardware.faketouch
android.hardware.usb.accessory
android.hardware.touchscreen.multitouch.distinct
android.hardware.microphone
android.hardware.location.gps
android.hardware.camera.front
android.software.live_wallpaper
android.hardware.sensor.accelerometer
android.hardware.touchscreen
glEsVers=2.0
JavaProperties
java.vendor.url: [Removed, under 10 posts]
java.class.path: .
java.class.version: 50.0
os.version: 2.6.34
java.vendor: The Android Project
user.dir: /
user.timezone: null
path.separator: :
os.name: Linux
os.arch: armv7l
line.separator:
file.separator: /
user.name:
java.version: 0
java.home: /system
Mount points
MountPoint
Name Type Options
- /
rootfs rootfs rw
- /dev
tmpfs tmpfs rw,nosuid,relatime,mode=755
- /dev/pts
devpts devpts rw,relatime,mode=600,ptmxmode=000
- /proc
proc proc rw,relatime
- /sys
sysfs sysfs rw,relatime
- /acct
none cgroup rw,relatime,cpuacct
- /mnt/asec
tmpfs tmpfs rw,relatime,mode=755,gid=1000
- /mnt/obb
tmpfs tmpfs rw,relatime,mode=755,gid=1000
- /dev/cpuctl
none cgroup rw,relatime,cpu
- /system
ubi0_0 ubifs rw,relatime
- /data
ubi1_0 ubifs rw,nosuid,nodev,relatime
- /cache
/dev/block/mtdblock6 yaffs2 rw,nosuid,nodev,relatime
- /proc/bus/usb
none usbfs rw,relatime
I plan on rooting this thing. As soon as I get that sorted out I may post more.
Also we're dealing with a M805MC (Amlogic 8726-M3) chip instead of RockChip RK2918.
I have attached images of both chips.
The mfg is Shenzhen Yifang Digital Technology Co., Ltd. and the build location is Guangdong, China. I'm under 10 posts so that's why no links but I can produce them upon request.
Ok this is sort of important so I will try to get the link in here.
Drum roll please....
Source code:
openlinux.amlogic.com/wiki/index.php/Arm/Platform_Info/Information_for_8726M/Build_system_for_8726M_Howto
If a moderator would like to make that link hot, be my guest .
I also purchased one of these tablets on Black Friday. It was on sale for 80.00 at Big Lots....Unfortunately its missing Google Apps, so rooting it would be nice...Although I really have absolutely no idea what I am doing, I did get ADB working and was able to reboot the device into some type of stock recovery, so with that in mind, please let me know if there is anything I can do to help...
Also either the HDMI port is shot after using it for just a few minutes or I have a bad cable...It was nice while it worked though.
Not having Google Apps is a bummer, but using info I found here: http://forum.xda-developers.com/showthread.php?t=1895040 I was able to get Gmail, Google Voice, Google Drive, Google Music, and Google + working. I also tried installing Google Talk, but ended up doing a factory reset because after I installed it...all the other Google Apps I had installed started crashing and I wanted to just start from scratch.
joelee100 said:
I also purchased one of these tablets on Black Friday. It was on sale for 80.00 at Big Lots....Unfortunately its missing Google Apps, so rooting it would be nice...Although I really have absolutely no idea what I am doing, I did get ADB working and was able to reboot the device into some type of stock recovery, so with that in mind, please let me know if there is anything I can do to help...
Also either the HDMI port is shot after using it for just a few minutes or I have a bad cable...It was nice while it worked though.
Not having Google Apps is a bummer, but using info I found here: http://forum.xda-developers.com/showthread.php?t=1895040 I was able to get Gmail, Google Voice, Google Drive, Google Music, and Google + working. I also tried installing Google Talk, but ended up doing a factory reset because after I installed it...all the other Google Apps I had installed started crashing and I wanted to just start from scratch.
Click to expand...
Click to collapse
I know I already clicked thanks but seriously, thanks again man. I don't think I personally have the skillset to root this thing so I humbly tip my hat to whomever gets it done. I do know that shutdown then vol up + plug usb in puts it in jtag mode . Shows as 'M3-CHIP' in devmgmt.msc (M3 being the CPU revision)
Sent from my Next8P12 using XDA Premium HD app
joelee100 said:
I also purchased one of these tablets on Black Friday. It was on sale for 80.00 at Big Lots....Unfortunately its missing Google Apps, so rooting it would be nice...Although I really have absolutely no idea what I am doing, I did get ADB working and was able to reboot the device into some type of stock recovery, so with that in mind, please let me know if there is anything I can do to help...
Also either the HDMI port is shot after using it for just a few minutes or I have a bad cable...It was nice while it worked though.
Not having Google Apps is a bummer, but using info I found here: http://forum.xda-developers.com/showthread.php?t=1895040 I was able to get Gmail, Google Voice, Google Drive, Google Music, and Google + working. I also tried installing Google Talk, but ended up doing a factory reset because after I installed it...all the other Google Apps I had installed started crashing and I wanted to just start from scratch.
Click to expand...
Click to collapse
I purchased 3 of these on Black Friday and have been unable to root them because of the aml8726-m34 chip. How did you get ADB working? What driver did you use? How did you get into recovery? I didn't think these tablets had any recovery interface.
I'm glad to hear that you did have some luck installing some of the google apps. Thanks for posting!
shaunmt said:
I purchased 3 of these on Black Friday and have been unable to root them because of the aml8726-m34 chip. How did you get ADB working? What driver did you use? How did you get into recovery? I didn't think these tablets had any recovery interface.
I'm glad to hear that you did have some luck installing some of the google apps. Thanks for posting!
Click to expand...
Click to collapse
I got in with the generic Google USB driver pesonally. You won't have root access though. Typing su from shell just gives a message about su not being found in the bin folder. Recovery is vol up + power or you can get there by putting a 3rd party zip on the sd card and then to to the upgrade app. It won't work because it's stock recovery. Oh, and for recovery to even see a .zip file it has to be on an external sd card.
Sent from my Next8P12 using XDA Premium HD app
---
[Update]
I've created a thread here to get people's attention as most people (like I was at first) are confusing this for the Next8SE or other Nextbooks. Hopefully the issue having it's own address will help make the information gathering process quicker.
mascondante said:
I got in with the generic Google USB driver pesonally. You won't have root access though. Typing su from shell just gives a message about su not being found in the bin folder. Recovery is vol up + power or you can get there by putting a 3rd party zip on the sd card and then to to the upgrade app. It won't work because it's stock recovery. Oh, and for recovery to even see a .zip file it has to be on an external sd card.
Sent from my Next8P12 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the tips! I'll try to get a rom dump tonight!
Anytime. I've shot Yifang/Nextbook an email asking for their source code. Hopefully they will comply as firmware does have software covered under GPL.
Also I brought up Netflix. Several Nextbook devices have a firmware update to address the issue. I'm assuming whatever the bug was, it was migrated inadverently to this device's code. Can I get some confirmation from other users that this is a shared issue? Thanks.
Finally, I noticed there is a Nextbook w/ Google Play so I also inquired about Gapps/Play being included in a future update. I will relay whatever information I recieve.
Sent from my Next8P12 using XDA Premium HD app
shaunmt said:
I purchased 3 of these on Black Friday and have been unable to root them because of the aml8726-m34 chip. How did you get ADB working? What driver did you use? How did you get into recovery? I didn't think these tablets had any recovery interface.
I'm glad to hear that you did have some luck installing some of the google apps. Thanks for posting!
Click to expand...
Click to collapse
I also pretty sure I used the generic Google USB driver. With the tablet turned on and usb debugging enabled I plugged it into the computer and then I updated the driver in device manager and then ADB worked...using the command "adb reboot recovery" got me into recovery...
Also, worth noting I guess, if my memory is correct...I think Windows 7 searched the internet and automatically installed some type of ACER driver. The Acer driver may have also worked, but I got rid of it and went with the generic Google driver(since it obviously wasn't an Acer device)...
Also, I noticed that the OP was able to flash a rom using the RKAndroid update tool, which is used for flashing firmware to a Rockchip based Android tablet. Are we able to confirm what chip the original posters device is running? I ask because it seems, like mascondante pointed out, that the next8p12 has shipped with different chips over time? The black Friday ones running the armlogic M3-chip and the earlier ones being a Rockchip RK2918?
joelee100 said:
I also pretty sure I used the generic Google USB driver. With the tablet turned on and usb debugging enabled I plugged it into the computer and then I updated the driver in device manager and then ADB worked...using the command "adb reboot recovery" got me into recovery...
Also, worth noting I guess, if my memory is correct...I think Windows 7 searched the internet and automatically installed some type of ACER driver. The Acer driver may have also worked, but I got rid of it and went with the generic Google driver(since it obviously wasn't an Acer device)...
Also, I noticed that the OP was able to flash a rom using the RKAndroid update tool, which is used for flashing firmware to a Rockchip based Android tablet. Are we able to confirm what chip the original posters device is running? I ask because it seems, like mascondante pointed out, that the next8p12 has shipped with different chips over time? The black Friday ones running the armlogic M3-chip and the earlier ones being a Rockchip RK2918?
Click to expand...
Click to collapse
All Nextbook 8 Premium SE roms I've found online were for the RK2918 chip using the RKAndroid tool... it might be possible to modify the Rockchip driver to recognize the AML8726-M3 chip, and maybe even flash one of the available roms, but it almost certainly wouldn't boot.
I wonder if the Bin4ry tool from this thread will work on these? It looks like it should work on anything with ADB working.
http://forum.xda-developers.com/showthread.php?t=1886460
shaunmt said:
All Nextbook 8 Premium SE roms I've found online were for the RK2918 chip using the RKAndroid tool... it might be possible to modify the Rockchip driver to recognize the AML8726-M3 chip, and maybe even flash one of the available roms, but it almost certainly wouldn't boot.
I wonder if the Bin4ry tool from this thread will work on these? It looks like it should work on anything with ADB working.
http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
I tried that tool and it didn't work, although it seemed to recognize the device...But I don't think I tried it while the device was actually turned on and booted(I'm not 100 percent sure), rather I think I tried it when I the device was in what i believe was jtag mode...I'll try again later.
EDIT: Crap...I tried while booted and having adb working...No dice...
joelee100 said:
I tried that tool and it didn't work, although it seemed to recognize the device...But I don't think I tried it while the device was actually turned on and booted(I'm not 100 percent sure), rather I think I tried it when I the device was in what i believe was jtag mode...I'll try again later.
EDIT: Crap...I tried while booted and having adb working...No dice...
Click to expand...
Click to collapse
I tried it using option 1 and ended up with a boot loop after the first splash screen. Was able to boot to recovery and do a factory reset.
Tried it with option 2 and it went through the process with several errors and booted ok, but did not achieve root.
I've also tried using recovery to install signed update packages with superuser and busy box, or even just gapps, but it refuses everything, indicating that signatures can not be verified successfully.
I'm currently trying to find a way to get read/write access in ADB or ADB shell, as this seems to be the big issue.
I agree, it also looks like ADB is the prevalent obstacle here. I'd like to at the very least get Android Market and all the crapware off this thing. I told someone this would be a great buy for a christmas present at BigLots as I was under the impression, after reading up on the RK29 devices, that they were rootable and I could get a custom rom onto it for them. I don't want to be the bearer of bad news!
amesfan said:
I agree, it also looks like ADB is the prevalent obstacle here. I'd like to at the very least get Android Market and all the crapware off this thing. I told someone this would be a great buy for a christmas present at BigLots as I was under the impression, after reading up on the RK29 devices, that they were rootable and I could get a custom rom onto it for them. I don't want to be the bearer of bad news!
Click to expand...
Click to collapse
I don't think there is anything we can do with these without an official update.zip from Nextbook.
I'm not talented enough to 'crack this nut' solo but I will keep looking across the web for a potential solution. I've been under the weather; Sorry for not staying mode on top of this.
I'm guessing the jtag mode is the key here. I'll keep looking.
Sent from my Next8P12 using XDA Premium HD app
mascondante said:
I'm not talented enough to 'crack this nut' solo but I will keep looking across the web for a potential solution. I've been under the weather; Sorry for not staying mode on top of this.
I'm guessing the jtag mode is the key here. I'll keep looking.
Sent from my Next8P12 using XDA Premium HD app
Click to expand...
Click to collapse
I got this response from Nextbook today concerning the Netflix update:
Thank you for the email. Please note, we're experiencing Technical difficulty with the
Next8P12 models that have an Android OS system level of 4.0.4. The Netflix Update
was issued for the Android OS systems with 4.0.3 models. Therefore, the configuration
of the update is unable to be recognized by the 4.0.4 OS units. However, we have
contacted Netflix to provide to us a patch for this model. We appreciate your understanding,
patience and apologize for the inconvenience.
When that update becomes available, it will likely be packaged as an update.zip (Like the existing one), which can be modified to give us root access.

[Q] Hardware Wifi Failure?

Hello, I was given a Gtablet by a friend. Everything is in proper working order except for the wifi. The wifi will endlessly scan, never pulling up any SSIDs. Here's what I've done to troubleshoot:
Ascertained flight mode was off (it was)
Enabled wifi through the developer options (Did nothing)
Manually enter SSID/Security information (Claims that SSID is not in range)
Reloaded the OS (He had VEGAn Tab on there. I reloaded the 5.1 Beta. I don't know what version he had on there, oops.)
After a clean install I have the exact same issue, which leads me to believe it is a hardware issue rather than a software issue. Is this common? Am I forgetting something? Would loading an entirely different ROM be of any use or do they also use the same driver?
My apologies if this has been answered previously, but in all my searching I can only find people who have this problem temporarily; a reboot fixes it for them. I haven't been able to find someone who has had this as a persistent issue.
JungleWallace said:
Hello, I was given a Gtablet by a friend. Everything is in proper working order except for the wifi. The wifi will endlessly scan, never pulling up any SSIDs.
Click to expand...
Click to collapse
I'll have to look at some logs to ascertain what your WiFi problem is.
Run the commands in this post (after rebooting the tablet) and then post the text files that're created.
rajeevvp said:
I'll have to look at some logs to ascertain what your WiFi problem is.
Click to expand...
Click to collapse
Thanks, see attached are the logs as per request. As a side note, now that I have the terminal emulator on there I tried a few commands I dug up on the internet after I looked over the logs.
Code:
$ su
# ifconfig tiwlan0 up
# ifconfig eth0 up
Both gave an error message
Code:
error: SIOCGIFFLAGS (No such device)
Also
Code:
# svc wifi enable
did not solve my issues. Oh well.
FYI:
JungleWallace said:
...I tried a few commands I dug up on the internet after I looked over the logs.
Code:
$ su
# ifconfig tiwlan0 up
# ifconfig eth0 up
Both gave an error message
Code:
error: SIOCGIFFLAGS (No such device)
Click to expand...
Click to collapse
The wireless LAN interface name on the gTab is wlan0. Hence your error messages: "No such device" for the ifnames tiwlan0 and eth0. (The latter would work for the ethernet I/F on the dock--if you had one connected.)
Also
Code:
# svc wifi enable
did not solve my issues. Oh well.
Click to expand...
Click to collapse
1. You have to look at the Android system logs (using logcat) to see the result of that svc command.
2. Your Android logs indicate that your WiFi interface is a) disabled at startup and b) then not enabled thereafter:
Code:
01-07 23:21:10.429 V/ConnectivityService( 990): Starting Wifi Service.
01-07 23:21:10.429 I/WifiService( 990): WifiService starting up with Wi-Fi [B]disabled[/B]
Suggestions:
Since this now looks like a ROM problem (ie. not HW):
1. See this thread. Run the script to disable Airplane Mode which might be causing your problem. If that doesn't work, try step 2:
2. Boot into CWM and then a) Format /cache and b) Repartition the Internal SD card (take the external one out first).
You'll lose all your current apps and data with this step, essentially reverting to a "fresh" install of your ROM.
Re-setup WiFi, time & date and other things again.
If step 2. doesn't work, report back next year, and I'll give you more commands to run then.
rajeevvp said:
If step 2. doesn't work, report back next year, and I'll give you more commands to run then.
Click to expand...
Click to collapse
Negative. Ran the airplane fix script, nothing. Reset cache/re-partitioned, still nothing. It's still endlessly scanning/shutting off/scanning.
JungleWallace said:
Negative. Ran the airplane fix script, nothing. Reset cache/re-partitioned, still nothing.
Click to expand...
Click to collapse
OK. Not one of the common simple problems, then.
It's still endlessly scanning/shutting off/scanning.
Click to expand...
Click to collapse
This is puzzling because from your last logs, it doesn't look like the wlan kernel driver was even loaded, so no AP scanning should be possible. A little background will clarify what I mean.
On all the 2.6.32.x kernels for the gTablet, the wlan driver is not compiled into the kernel. Instead, it is built as a separate kernel module which is loaded and unloaded as needed by Android (from the files in /system/lib/hw/wlan/). When the wlan driver is loaded both the kernel (dmesg) and Android (logcat) will show some characteristic messages and until the driver is inserted into the kernel no AP scanning, or other wireless functions, should be possible. And, no wlan driver-related messages in your logs tells me that the driver was likely not loaded. (Also, only after the wlan driver is loaded does it check and initialize the wireless HW. So, only after its been loaded, strictly speaking, can we rule out a HW problem.)
Sometimes the Android logs are not complete, so I want to you setup ADB on your PC, enable USB debugging on the gTablet (Setting > Applications > Development) and collect the Android logs like this from now on:
1. Power off gTab; attach the USB cable to it.
2. Open a CMD.exe window on the PC, then run this command (and keep the window minimized):
Code:
C:\> [B]adb logcat -v time > logcat.txt[/B]
After all the tests/commands have been done, restore this window and press Ctrl-C to kill ADB and terminate Android log collection.
3. Power on the gTablet. The ADB command will wait for the gTablet and keep collecting logs on the PC.
Post also the output of these commands:
Code:
C:\> [B]adb shell dmesg > dmesg.txt[/B]
C:\> [B]adb shell lsmod > lsmod.txt[/B]
C:\> [B]adb shell "cd /; find system -type f -print0 | xargs -0 sha1sum" > sha1sum.txt[/B]
Is this the ROM you currently have?
Have you applied the VEGAn 1.00 beta 5.1.1 supplement also?
rajeevvp said:
OK. Not one of the common simple problems, then.
.........
Is this the ROM you currently have?
Have you applied the VEGAn 1.00 beta 5.1.1 supplement also?
Click to expand...
Click to collapse
That was the current ROM I was using. I had not applied the supplement yet, but now I have. Still the same issue. Here are the logs.
JungleWallace said:
That was the current ROM I was using. I had not applied the supplement yet, but now I have. Still the same issue. Here are the logs.
Click to expand...
Click to collapse
In this one I can see the kernel WiFi driver being loaded, and the driver is not reporting any HW chip, SDIO bus, or other errors:
Code:
<4>[ 23.485281] sdio_reset_comm():
<4>[ 23.503617] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 23.676913] Firmware version = wl0: May 17 2010 22:38:50 version 4.218.223.1
<4>[ 23.887647] wlan0: Broadcom Dongle Host Driver mac=e0:2a:82:08:3e:81
<4>[ 23.894047] Enter wl_control_wl_start
<4>[ 23.897864] Exited wl_control_wl_start
<4>[ 23.907103]
<4>[ 23.907109] Dongle Host Driver, version 4.218.223.1
As far as the kernel driver is concrned, everything looks OK, but the Android logs still don't show any SSID associations.
What're the exact outputs of these commands? (You can post a screenshot. Mask the psk= value from the 1st output, if present)
Code:
C:\> [B]adb shell "fgrep -v '#' /data/misc/wifi/wpa_supplicant.conf | tr -s '\n'"[/B]
ctrl_interface=wlan0
update_config=1
...
C:\> [B]adb shell wpa_cli -i wlan0 driver rssi[/B]
...
C:\> [B]adb shell wpa_cli -i wlan0 driver linkspeed[/B]
LinkSpeed [I]nn[/I]
C:\> [B]adb shell wpa_cli -i wlan0 scan[/B]
OK
C:\> [B]adb shell wpa_cli -i wlan0 scan_results[/B]
bssid / frequency / signal level / flags / ssid
aa:bb:cc:dd:ee:ff 2452 185 [WPA2-PSK-CCMP] [I]YourSSID[/I]
Collect also the dmesg and logcat outputs as before.
[/FONT]
rajeevvp said:
What're the exact outputs of these commands? (You can post a screenshot. Mask the psk= value from the 1st output, if present) [...] Collect also the dmesg and logcat outputs as before.
Click to expand...
Click to collapse
See attached. Ignore my syntax errors that I underlined. I was typing wlan instead of wlan0.
JungleWallace said:
Ignore my syntax errors that I underlined. I was typing wlan instead of wlan0.
Click to expand...
Click to collapse
Those are OK since you've corrected them. But, these commands you'll have to redo:
1. In the first command (fgrep ... | tr), you've typed a '/' (forward slash) instead of what I've given in the example, which is a '\' (back-slash) character.
The correct character will remove all those blank lines. But, this is a minor typo compared to:
2. The last 2 commands (wpa_cli scan* ...), which you'll have to redo. This time without the extraneous driver argument (again, see the example)--which turns it into a completely different (and non-existent) command. This is why the output doesn't look like what I've shown.
Instead of typing the commands in manually, select and copy the command lines from the browser and paste them into the shell window.
You might also want to increase the no. of columns that CMD.exe displays: Right-click on the title-bar; choose Properties; select Layout; increase the no. of Columns to, let's say, 150.
3. That dmesg.txt file is not very useful because you've not rebooted the tablet before issuing that command.
The kernel has a fixed-size message buffer, so all the HW initialization messages printed only at system boot will be overwritten by later, and irrelevent, messages as time passes. From the timestamps, it looks like your tablet's been on for a couple of weeks, at least--I can't see any of the earlier boot-up messages.

[Q] How to obtaing GPU and RAM frequency from the Android filesystem

I would like to know how to read de GPU and RAM operation frequency from the Android filesystem. I know that I can obtain the CPU frequency from files such as:
Code:
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq
I'm trying to do that with Pandaboard, but in fact I need to do it in more development boards (Odroid-PC, Beagleboard-xM, Sabreboard and Wandboard).
Any idea? at least how to do that with an app? I tried with CPU-z but it do not has this information. Also, I tried with commands such as dumpsys without success.
Thanks in advance.

Elo Intellitouch 2700 on android 4.2

Hi everyone,
I need soem hints - regarding registering a elo touch on the Android arm sys,
idc file exists: /system/usr/idc/Vendor_04e7_Produuct_0020.idc (device naamed after the Android docs scheme - Vendor ID and Product ID are correct, double checked it with dmesg and logcat.
content of the file:
device.internal 1 #(tried it with 0 too)
touch.deviceType = touchScreen
getevent on the correct device lists some input - but the display does not change.
how can I link the input device?
any clue may help!
thank you

Categories

Resources